| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| computers [2023/07/13 08:48] – [Avanaa] ajung | computers [2023/09/18 12:45] (current) – ajung |
|---|
| ====== Lab Computers & peripheral accessories ====== | ====== Lab Computers & peripheral accessories ====== |
| |
| For an internal inventory of computers and peripheral accessories, see the listing on our [[https://docs.google.com/spreadsheets/d/115PalLdIsIVjuEWRhEMWOy4boxrqDbf1RRigwBKVZpk/edit?usp=sharing|Google Sheet]]. | For an internal inventory of computers and peripheral accessories (and associated primary users), see the listing on our [[https://docs.google.com/spreadsheets/d/115PalLdIsIVjuEWRhEMWOy4boxrqDbf1RRigwBKVZpk/edit?usp=sharing|Google Sheet]]. |
| |
| Our lab computers have been purchased to meet the lab's specific needs. For environmental sustainability reasons, the lab does not provide a personal computer for each graduate student. Rather, lab computers are provided to the student based on their project and equipment needs. | Our lab computers have been purchased to meet the lab's specific needs. For environmental sustainability reasons, the lab does not provide a personal computer for each graduate student. Rather, lab computers are provided to the student based on their project and equipment needs. |
| **AI:** Students working on responsible AI projects and those needing computer graphics processing power for robotics projects will have access to our shared GPU-machine, [[computers#avanaa|Avanaa]] (see further info below). Our ML training needs are occasional and small compared to other labs whose main research contribution is in ML. Avanaa more than suffices the training needs of the lab. However, if you find that you need much more compute power for specific projects, you can ask to use larger shared resources that the lab has access to (e.g., Compute Canada, shared compute clusters in France via ILLS, Mila etc.). Don't be shy to ask about these larger compute resources if you think your project belongs to this latter category. | **AI:** Students working on responsible AI projects and those needing computer graphics processing power for robotics projects will have access to our shared GPU-machine, [[computers#avanaa|Avanaa]] (see further info below). Our ML training needs are occasional and small compared to other labs whose main research contribution is in ML. Avanaa more than suffices the training needs of the lab. However, if you find that you need much more compute power for specific projects, you can ask to use larger shared resources that the lab has access to (e.g., Compute Canada, shared compute clusters in France via ILLS, Mila etc.). Don't be shy to ask about these larger compute resources if you think your project belongs to this latter category. |
| |
| As we belong to the Center for Intelligent Machines, we follow the computing policies you signed when you signed the CIM access request form. The best practice is to use the CIM username and password to access lab machines. | As we belong to the Center for Intelligent Machines, we follow the computing policies of the Centre. Request access to CIM accounts by following the [[https://wiki.cim.mcgill.ca/doku.php?id=cimaccount|CIM access request process]]. The best practice is to use the CIM username and password to access lab machines. |
| | |
| | ===== GPU Machines at Mila ===== |
| | For those of you who drop by Mila regularly, we have access to Mila Tech Lab and the GPU machines available there. This is used as a first-come first-serve resource with no backup (i.e., you'll want to back up all your work at the end of each session to the lab backup system). Pls see Mila's intranet for more detail. |
| ===== Avanaa ===== | ===== Avanaa ===== |
| Avanaa is our main GPU-machine. As GPU resources are in high demand and most GPU-needs are occasional, Avanaa is a shared resource for the RAISE lab (and our friends). | Avanaa is our main GPU-machine. As GPU resources are in high demand and most GPU-needs are occasional, Avanaa is a shared resource for the RAISE lab (and our friends). |
| |
| === Best Practices for Happy Sharing of Avanaa === | === Best Practice for Happy Sharing of Avanaa === |
| |
| **Communicate:** Given that majority of the work is done by multiple individuals remote-accessing the computer, all users of the machine are expected to coordinate with other users when they have specific computing needs that will interrupt others' work, or need dedicated training time for days etc. Feel free to let AJung know if such needs come up that will greatly interrupt others' access, but it is mainly your responsibility to communicate with other users and support each other's research needs. See below for the active users list for Avanaa-related matters that affect others. Request to add your name to the list if yours is missing. | __Communicate:__ Given that majority of the work is done by multiple individuals remote-accessing the computer, all users of the machine are expected to coordinate with other users when they have specific computing needs that will interrupt others' work, or need dedicated training time for days etc. Feel free to let AJung know if such needs come up that will greatly interrupt others' access, but it is mainly your responsibility to communicate with other users and support each other's research needs. See below for the active users list for Avanaa-related matters that affect others. Request to add your name to the list if yours is missing. |
| |
| **Take care:** Power interruptions are frequent at McGill, forcing us to unplug the machine with days of notice in order to protect our expensive electronic equipment. Avanaa is no exception. Schedule your compute tasks accordingly and volunteer to unplug and help protect the machine when needed. | __Take care:__ Power interruptions are frequent at McGill, forcing us to unplug the machine with days of notice in order to protect our expensive electronic equipment. Avanaa is no exception. Schedule your compute tasks accordingly and volunteer to unplug and help protect the machine when needed. |
| |
| **Be responsible:** For any ML tasks, it's easy to assume that you can mix some data, train different models, tweak here and there, and end up with some cool results at the end of the day. | __Be responsible:__ For any ML tasks, it's easy to assume that you can mix some data, train different models, tweak here and there, leave the machine training over the nights/days and end up with some cool results. This is the wrong way to approach ML tasks. As is discussed across the ML community, model training has a non-negligible cost to the environment. **If you do not know how to calculate the complexity of your program, estimate and monitor the feasibility and size of your training task**, then you are likely blindly trying to throw ML at a problem that will do more harm (including waste of your time) than good. In this case, you are not ready...! Go back to the basics, and come back when you are ready. |
| |
| === Specs === | === Specs === |
| |
| === Active Users === | === Active Users === |
| * Sudo access: [[https://www.raiselab.ca/people/lixiao-zhu|Lixiao Zhu]], AJung | * Sudo access: [[https://www.raiselab.ca/people/lixiao-zhu|Lixiao Zhu]] |
| * Priority users/uses: | * Priority users/uses: |
| * [[https://ogdenslake.ca/about/|Michael Smith]] (Ph.D. candidate with Prof. Frank Ferrie) | * [[https://ogdenslake.ca/about/|Michael Smith]] (Ph.D. candidate with Prof. Frank Ferrie) |
| * [[https://www.raiselab.ca/people/lixiao-zhu|Lixiao Zhu]] | * [[https://www.raiselab.ca/people/lixiao-zhu|Lixiao Zhu]] |
| | * Other RAISE Lab members toward their research needs (currently none) |
| * Secondary users/uses: | * Secondary users/uses: |
| | * RAISE Lab members for their course projects |
| * | * |
