Download
1 / 3
30 likes | 146 Views
Announcements/Updates . CSL Usage: (150%/133% thresholds) Development: 197%/117% for 30/90 day Production: 134%/104% for 30/90 day Marika will ask Dave Hart to increase the thresholds if the machine truly is underutilized (as long as this could be done for the rest of the allocation period).
E N D
Announcements/Updates CSL Usage: (150%/133% thresholds) Development: 197%/117% for 30/90 day Production: 134%/104% for 30/90 day Marika will ask Dave Hart to increase the thresholds if the machine truly is underutilized (as long as this could be done for the rest of the allocation period). Co-chairs will notify their working groups to run in economy for the month of November. Integrations – LE Runs, Last Millennium, CLM4.5-CAM5 Coupled Run, Others? Last millenium 6 runs in progress: full forcing, volcanic only, solar only, GHG only, Land use/cover only, and one other. These runs are out a few hundred years. 850 control run mostly done CLM4.5 coupled run Amazon forest about 1/3 as healthy as it should be in the coupled run. Since this is the biggest carbon stock on the planet, this is a big deal. Same problem exists in 2 deg run. Dave L is going through a sequence of sensitivity experiments to understand it. It seems like there is a feedback: low RH -> low leaf area, and things die back. Does not seem to be due to precipitation... now looking at other possible factors Large ensemble To relieve glade space, plan to delete the original history files, only saving time slices. This means: if there's anything you want to do with the raw history files, do that now! They're doing finishing touches on BAMS proposal. Note that only AMWG and OMWG are doing diagnostics on these – due to lack of liaisons for the other groups. But they have confirmed that they're saving the files needed to run the other diagnostics in the future.
Announcements/Updates (continued) CSEG (Decaf?!?) Coffee Talk https://trello.com/b/y8bYsqB0/cseg-tutorial-ideas • This would be a quick way to communicate to scientists • Start in January • Talks would compliment written instructions • Record and archive • Frequency – every 2 months (Brown Bag) Rich: Would be good to have a longer talk on coding standards, maybe bringing more uniformity and quality across component Cecile: important to have scientists involved in development of this. She volunteers to help with this. Gokhan: points out that some software engineering changes (e.g., in coupler) have made it harder to do some science changes. This points to the need for a 2-way dialogue. Trello We are moving a lot of the software engineering planning to trello. e.g., we have cpl, clm, cam boards showing upcoming tasks & projects
Announcements/Updates (continued) • New release update procedure • CSEG realized that, if we could have a portion of our development repo that was publicly readable, that would streamline the release process and make it less time-consuming. • This makes the process of creating release tags more similar to what we do for CESM beta tags. • Since it's easier to do release updates, we can do this more frequently (how frequently is TBD) • Mariana: From CSEG's point of view, release updates will include machine updates & bug fixes – NOT new science changes, unless the co-chairs decide otherwise. • Gokhan: Would this reduce human cost of creating releases, especially related to testing? Mariana: it might reduce test costs, because we won't have to rerun the whole test suite if the fixes are limited to a subset of the system. • Keith: An example: BGC group wants to get CMIP compsets into the 1.0 series. Does this change this? Mariana: no & yes: we would first target the 1.2 series, but then we can consider doing the 1.0 series. Jim: if you were willing to do a large chunk of the work to put this in & test it, this might be doable. JF: thinks we're opening a can of worms if we let new science come in. Jen: need to prioritize, and sees machine updates for yellowstone as a higher priority than science updates that will only benefit a small set of people. • Marika: part of this is seeing how much work reduction this really means, then we can revisit what it means in terms of frequency of release updates. • Gokhan requests a record of how much time is spent on a release update. • Mike Levy: There currently isn't clear documentation of when a minor release will happen, and what the process is for getting a bug fix into the next minor release • Marika: Note that we previously said we weren't going to have minor releases (except for the annual release), so this is allowing for the possibility that we might have some now
