Attendees:
Rob G., Emelie, Marko, Chander, Suchandra, Bala, David, Kyle (operations), Mats, Lauren
Rob: Work items: put together a program, dry run (locally), define format, compile materials. Bala is going to instructors training (Sept 22-23). There is a workshop here on campus as well that Suchandra and Bala are going to attend. We discussed having first SWC workshop in WI - a lot of resident expertise on SWCarpentry parts.
Chander: Can we avoid last week of Jan? (There is an xrootd workshop in San Diego).
Lauren: UWM is having their own SWC bootcamp the week before classes start in Jan (12-13). Bootcamp is just 2 days. There would be some overlap/repeating between this and the OSG SWC workshop.
Rob: We should circulate that as tentative dates and see what people think. (Jan 14-16 Wed-Fri). Try to decide by next time what curriculum should be. And decide what kind of infrastructure to use.
Lauren: Have everyone use OSG Connect.
Emelie: Can prepare intro to OSG slides.
Bala: Can prepare sample applications/tutorials for OSG.
Lauren: Will get github repo set up (fork UWM SWC materials to OSG).
Rob: We also need to advertise this within OSG. Should it be free? Or should we charge?
Lauren: It is up to the University. Charging a nominal fee helps avoid no-shows. Can spend the money on coffee, etc. Who do we want audience to be?
Rob: What is target capacity?
Lauren: About 30
Rob: Probably about 6 helpers.
Mats: Might want to consider also filming it. The biggest problem is usually sound.
Lauren: WID uses online service similar to adobe connect.
Rob: We should probably have data-driven topics and workflow topics. Would it make sense to have simple Dagman example?
Mats: Yes. Another issue: The core SWC material is in ipython notebook. Switching to OSG throws away part of that buildup. Come up with a way to transition (so it doesn't feel like starting over).
Lauren: We don't use ipython notebook for UWM SWC bootcamp. Do we want people to start out logged into osgconnect and do everything there? Or use ipython notebook on their laptop?
Mats and Rob agree it would be best to start out on osgconnect. Will have to convert curriculum from ipython notebook or use UWM software carpentry curriculum. Other benefit of using UWM curriculum: UW instructors can help with the SWC part.
Rob: Bala to register workshop in SWC, once dates are certain.
Lauren: Can update us on dates (check them with WID). Caution on advertising and opening up registration until 4 weeks ahead of time. Less drop-outs.
Chander: Caveat - this would not allow time for making travel plans. Should probably not wait any later than Dec 1st.
Come back in 2 weeks to discuss.
Emelie: Question for Mats/Suchandra about pre-loading modules. Would there be conflicts between modules if they are all pre-loaded?
Mats: The modules themselves would not be pre-loaded, just the modules environment. To pre-load individual modules would require something in condor submit file like a list of modules to pre-load. Is this even technically feasible?
As far as automatically sourcing the setup script for loading the modules environment, one issue is how to deal with failures. But other than that, would be simple to implement.
Marko: Invoking the setup script is like changing the environment for everybody. Is that okay?
Mats: It is not really changing the environment (not changing paths, etc). Just adding to it.
Suchandra: Added madgraph module requested by a user. Adding a couple more modules this week: PBsuite, ECtools. Also finished up the list of software to install.
Marko: Suchandra, do you have a recipe for creating modules?
Suchandra: I have been adding compilation instructions for each module/package to the repo ('recipes'). Will send around directions for creating modules soon.
Next meeting in 2 weeks.
Coordinates:
Tuesday September 16th at 2:00 p.m. Central Time
Dial-in #: 866-740-1260
Access code: 6643420#