The DEC Code of Conduct¶
The DEC cluster is a shared computing environment where collaboration meets raw power. To keep things fair, efficient, and friendly, we've assembled this set of usage guidelines. By following these rules, you help ensure that everyone gets a fair shot at the system's resources.
1. Be Transparent¶
- Name your jobs like a pro. Avoid
run.sh
and aim foralign_euclid_march24.sh
. - If your job is long or demanding, give everyone a heads-up. Use comments, issue tracking, or even the mailing list like it's 1999.
2. Resource Sharing¶
- You can use more than 2–3 nodes — nobody's stopping you.
- But if your job:
- Uses many nodes ie > 4 nodes
- Run for a long time ie > 2 days
Please be a good neighbor and let us know. It’s not a rule, it’s just a nice thing to do.
Create an issue on GitLab to declare your intentions: DEC GitLab Issues with a tag node-reservation
(see below for details).
(And if you’re not sure, just ask by mail. We don’t bite... except on Fridays.)
3. Respect the Disk Space¶
- No quotas, no worries — but don’t be a data hoarder.
- Use
/datadec
for active personal projects and/loftdec
for active collaborations and/roofdec
for archiving (see Disk Space and Storage Options). - If you need more than 10 TB, tag your reservation as
disk-reservation
(see below for details).
4. Monitor Like a Pro¶
- Use
htop
,ps
, or your favorite command-line incantation. - Kill zombie processes. They don’t belong in science.
5. Clean Up After Yourself¶
- Don’t leave
/tmp
looking like/var/chaos
. - Delete what’s not needed. Archive what is.
6. Be Human¶
- If something breaks, say so. If someone uses 10 nodes silently, ask kindly.
- Use
decusers@cppm.in2p3.fr
for group updates. It’s not Slack, but it works.
Thanks for keeping things cool (only the CPUs should be hot).
Reservation System¶
We track reservations using GitLab Issues, just fill out an issue here: DEC GitLab Issues (you need to be logged in with your EduGain account).
We’ll maintain a shared calendar view here:
📅 DEC Reservation Calendar
Please use the following guidelines when creating a reservation issue:
Template¶
- Type:
Issue
(default) - Title:
Node reservation
and/orDisk reservation
- Description:
Please use the following template in markdown:
```markdown
- User: [Your DEC username]
- Project / Purpose: [Brief description of your project, e.g., “Euclid data reduction”]
- Resources: e.g., mardec12 to 14 and/or 15 TB in /datadec
- Dates: Start and end dates
- Additional Information: [Any additional information or requirements] ```
- Assignee:
Julien Zoubian
- Label:
node-reservation
and/ordisk-reservation
- Dates: Start and end dates
The “end date” is not a guillotine — it just tells the admin when to check in with you.