CRADC News and Announcements
June 23, 2008
Dear CRADC Researchers,
Please note these important announcements about CISER's CRADC computing system:
- The CRADC computing system will be down on Monday, June 30th from approximately 6:00PM to midnight(EDT, USA).
- The CISER billing begins on July 1st, 2008. For information on the new CISER cost recovery system, and how it may affect you, please see our Frequently Asked Questions page. (See tips for reducing or avoiding charges at http://ciser.cornell.edu/computing/TipsforCISERComputing.shtm )
- Rhodes Hall will be without electricity from July 15th 11PM - July 16th 6AM. CISER computing systems are on UPS and are not expected to be down, but user access may be limited.
Please let us know if you have any questions. Thank you for your cooperation.
May 19, 2008
Compute nodes available in the CRADC domain:
cradc201.cradc.cornell.edu
- OS: x64 bit Windows
- CPU: Four-Quad core (=16 CPUs)
- Memory: 128 Gigabytes
cradc202.cradc.cornell.edu
- OS: x64 bit Windows
- CPU: Four-Quad core (=16 CPUs)
- Memory: 128 Gigabytes
May 17, 2008
Dear CRADC Researchers,
This is a reminder that the CRADC computing system will be down Sunday, May 18th, from 7 AM until 10 AM (EDT, USA).
We are pleased to announce that during this downtime we will add one more new compute node CRADC202 to the system and would take all old nodes out of service. Therefore, when the system is back online you will have access to two compute nodes cradc201.cradc.cornell.edu & cradc202.cradc.cornell.edu each with 16 CPUs and 128 Gigabytes Memory.
May 5, 2008
Dear CRADC Researchers,
Due to CIT's planned network outage for all systems at Rhodes Hall, the CRADC computing system will be inaccessible on Sunday, May 18th, 2008 from 7 AM until 10 AM (EDT, USA).
Please plan your work accordingly.
4/17/2008 4:00PM(EDT,USA)
Dear CRADC Researchers,
Thank you all for your patience. We are pleased to announce the installation of one new compute node named CRADC201 for your research.
Due to hardware concerns, we have taken some of the old CRADC nodes out of the service. The old nodes still available for service include CRADC02, SIMULATOR and MADISON.
The details of the nodes are as follows:
cradc201.cradc.cornell.edu (new node)
- OS: x64 bit Windows
- CPU: Four-Quad core (=16 CPUs)
- Memory: 128 Gigabytes
madison.cradc.cornell.edu
- OS: 64 bit Windows
- CPU: 4
- Memory: 16 Gigabytes
simulator.cradc.cornell.edu
- OS: 32 bit Windows
- CPU: 8
- Memory: 4 Gigabytes
cradc02.cradc.cornell.edu
- OS: 32 bit Windows
- CPU: 2
- Memory: 4 Gigabytes
Please note that to access the SAS on a CRADC node, the researchers have to edit the properties of their SAS shortcut to point to their own copy of SAS.CFG file which was modified to create SAS -WORK under the researcher's authorized folder. Detailed instructions for the steps involved in this process are available inside CRADC nodes at http://info.cradc.cornell.edu/CRADC/computing/online_Help.shtml ( this link is accessible only inside the CRADC domain).
Let us know if something is not clear and we will be happy to help.
e-mail cradc_custodian-mailbox@cornell.edu
April 3, 2008
CRADC Computing System Downtime Thursday, April 17th from 6AM until 6PM
Dear CRADC Researchers,
Please note that the CRADC computing system will be down for maintenance on Thursday, April 17th from approximately 6:00AM until 6:00PM(EDT, USA). We thank you for scheduling your work to avoid this time period.
2/28/2008 4:00PM(EST, USA)
All CRADC compute nodes cradc01, cradc02, cradc04, simulator and madison are now back online.
2/28/2008 2:35PM(EST,USA)
The CRADC computing nodes cradc04, simulator and madison are now back online. We are still conducting maintenance on cradc01 & cradc02, and will let you know as soon as they are available. Thank you for your patience.
February 14, 2008
CRADC Computing System Downtime Thursday, February 28th from 8AM until Noon
Dear CRADC Researchers,
Please note that the CRADC computing system will be down for routine maintenance on Thursday, February 28th from approximately 8:00AM until 12:00PM(EST, USA). We thank you for scheduling your work to avoid this time period.