|> home > services > policies > code|
Code of Conduct
HPCx will be a service which is shared by a large number of people and projects. We are sure that users will be keen to cooperate as colleagues to ensure that this common resource is run fairly and efficiently.
The Code of Conduct will be a set of rules of etiquette which we commend to users in order to achieve this end. If you follow them you can be reasonably sure that you are not being a nuisance to colleagues in other projects or interfering with the smooth running of the system.
We don't plan to administer the service with a heavy hand. In our experience, when users become aware that what they are doing is causing problems to others, they are anxious to change this. However, if you ignore the Code of Conduct we will bring it to your attention, and if you do so seriously or constantly, we will take it up with your Principal Investigator. And if necessary, we will hold jobs, or even kill them, in order to keep the system as a whole operating smoothly.
The Code of Conduct will change as the service evolves.
Avoid the job submission loop It's a good idea to arrange for one batch job to submit its successor. But you need to avoid doing this when a job fails for some reason (for example, a file not being available), as this can result in the job submitting itself over and over again, and failing every time.
Avoid doing a lot of interactive work Instead of doing large compilations, data handling operations etc interactively, it's better to use the serial batch queues if possible. At present there are no limits on interactive use, but if it becomes too great as more users start work, we made need to impose them.
|http://www.hpcx.ac.uk/services/policies/code.html||contact email - email@example.com||© UoE HPCX Ltd|