Daily Bulletin Archive

December 18, 2012

The Mirage and Storm data analysis and visualization clusters have been scheduled to be retired on February 28, 2013. As previously announced, the current timeline for Bluefire will have that system being decommissioned on January 31, 2013. Users should plan their work accordingly.

The Mirage and Storm clusters will be kept around for an additional month after Bluefire so that users can wrap up their final analysis tasks and migrate data to the Yellowstone environment.

Most Mirage and Storm users should now have access to the Yellowstone environment and its Geyser and Caldera analysis clusters. Users are strongly encouraged to begin ramping up on that environment, while they focus on bringing their work on Mirage and Storm to a meaningful stopping point.

Users should review the Geyser and Caldera documentation at https://www2.cisl.ucar.edu/resources/geyser_caldera as well as the Yellowstone transition documentation at https://www2.cisl.ucar.edu/resources/yellowstone/transition.

Please contact cislhelp@ucar.edu if you have questions about Geyser and Caldera access.

December 13, 2012

The consulting office and help desk will close for a staff event Thursday, December 13 from 12:15 - 2:00.

Computing users may still submit tickets to cislhelp@ucar.edu and we will respond by Thursday afternoon.

December 13, 2012

Yellowstone users can now submit jobs to any of the standard queues, with the exception of the "capability" queue, which is limited to Accelerated Scientific Discovery (ASD) projects.

This change gives jobs from non-ASD users more opportunities to fill in around the ASD jobs, as well as to submit larger jobs.

Please keep in mind, however, that ASD jobs continue to have priority, and non-ASD users are encouraged to limit their work to smaller-scale jobs for the next two months. Large-scale jobs from non-ASD users may not be scheduled as quickly during this period.

December 13, 2012

Yellowstone users can now copy (cp) any files they need from Bluefire’s /ptmp and GLADE file systems to the new Yellowstone GLADE file spaces. Instructions are available at http://www2.cisl.ucar.edu/resources/yellowstone/quick_start#copy_files.

Before migrating your files, consult the GLADE File Spaces for Yellowstone documentation at http://www2.cisl.ucar.edu/resources/glade_yellowstone.

Please do NOT use HPSS as a temporary staging area for migrating files; it is difficult to recover tape space even after the files are deleted. If your files are already in HPSS, however, you can access them from Yellowstone via HSI or HTAR.

December 7, 2012

Along with the arrival of Yellowstone, CISL has deployed the new System Accounting Manager (SAM) application for managing allocations, user preferences, and accounting for resource use.

You can visit SAM at http://sam.ucar.edu/ and log in with your UCAR token or password.

Select User -> Preferences to view and set your primary group across CISL resources, your default project for HPSS, and your preferred login shell.

Select Reports -> Account Statement to view project information, allocations, and resource activity, including job-level details. Yellowstone and Janus use is reported daily; weekly HPSS usage will begin appearing soon.

SAM is very much a work in progress. CISL is actively working on expanding the reporting features, including 30/90 day reporting, and improve the user interface. If you encounter any errors or if you have any feedback and feature requests, please send them to cislhelp@ucar.edu.

December 4, 2012

CISL is pleased to announce that all users now have access to the Yellowstone system starting Monday, November 26. Based on feedback from early users and after completing major system updates, we are making a portion of the system available to all users for porting, testing, and preparing for the transition from Bluefire while we continue to improve the Yellowstone user experience.

Initially, general users will have access to approximately 648 nodes (10,368 cores) and can only submit jobs to the *economy* queue. Once CISL and IBM have completed further evaluation of the overall system's stability and some planned performance tests, we will lift these restrictions.

During Yellowstone's first two months, most of the system will be dedicated to supporting the 11 Accelerated Scientific Discovery (ASD) projects [http://www2.ucar.edu/atmosnews/big-data/first-accelerated-scientific-discovery] as they tackle major challenges in the geosciences. However, approximately 4 percent of the system -- roughly equivalent to the computational capacity of Bluefire -- will be available for other users to port their codes and conduct testing and small-scale runs.

For Bluefire users, CISL has provided a transition guide that highlights some key differences you will encounter on Yellowstone [http://www2.cisl.ucar.edu/resources/yellowstone/transition] and a quick-start guide [http://www2.cisl.ucar.edu/resources/yellowstone/quick_start] as part of the system documentation. Due to the possible high volume of requests, users are strongly encouraged to consult the Yellowstone documentation prior to submitting help requests.

We emphasize that Yellowstone is still a work in progress, and CISL and IBM are continuing to refine the user environment, install additional software, and resolve system problems that cause jobs to fail. Furthermore, the Geyser and Caldera clusters do not yet have their full complement of analysis and visualization software installed.

If you have any problems with the system or a request for software be installed, please send help requests to cislhelp@ucar.edu. We are particularly interested in learning about any job failures you may experience; please include system error messages in your help request.

November 27, 2012

We are relaying the following message from the CESM team about user interest in the CCSM3 models ported to Yellowstone. Please respond to the email indicated below.

CESM users,

We are soliciting information on who is hoping to run CCSM3 on NCAR supercomputing resources in the future. If you have plans to do so, please send an email to Barbara Ballard (bballard@ucar.edu).

Note that under the current policy, support for the CCSM3 model version has expired. Your input on CCSM3 usage will inform the project on whether and with what priority a CCSM3 port to the new Yellowstone system might occur.


Marika Holland

November 26, 2012

Date: Wednesday, December 5, 2012
Time: 8:30am- 12:30pm
Location: San Francisco Marriott
Room: Nob Hill A
Cost: FREE (refreshments will be served)
Registration: NONE REQUIRED
Organizers: John Clyne, NCAR
Only a few years ago advanced scientific visualization techniques were largely limited to the realm of visualization experts, and employed primarily as a communication aid to illustrate complex phenomena. Thanks to the commoditization of computer graphics hardware, and the emergence of mature, user-friendly, domain-focused software packages, scientific visualization is increasingly becoming an indispensible tool used by resarchers in their day-to-day efforts to analyze data and extract new insights. This workshop will provide an overview of some of the open source software packages that are available, and most relevant, to researchers in the geo-sciences. Attendees can expect to gain a basic understanding of the capabilities of these powerful visual data analysis environments; learn which tools may be most appropriate for their own needs; and have an opportunity to talk with tool developers, on-hand for the workshop.
Visual Data Analysis Wiki

November 21, 2012

No Scheduled Downtime: Bluefire, HPSS, DAV, ML GLADE, Firefly, Lynx

November 20, 2012

Starting November 12, Bluefire will no longer be enforcing allocation usage limits or 30/90 usage thresholds. The LSF scheduler will accept all jobs submitted against an active project number.

CISL will continue to track usage for reporting purposes, and the LSF scheduler will continue to enforce its fair-share policies. Namely, the scheduler will maintain the defined balance among University, NCAR, and Climate Simulation Laboratory activity and will ensure that no individual user can monopolize the system.

The premium and lrg_premium queues have also been disabled.

The decommissioning date for Bluefire has not yet been set. We plan to operate the system until at least the end of the year.