Date and Location
, 11am-12pm pacific.
Attendees
UW:
Princeton:
- IPAC:
- SQUARE:
- NCSA
- SLAC:
Goals
- To start getting on the same page with regards to butler, with focus on what butler really is, what it does, what its roles are, what APIs is has, and most importantly what it will and will not do in the future.
Discussion items
It'd be great if each team could cover features you think you "must have" in butler that are not available today, and features that would be nice-to-have but are not critical.
Time | Item | Who | Notes |
---|---|---|---|
5min | Intro | K-T or NateP or Jacek |
|
10min | UW |
| |
10min | Princeton | DRP Butler Requirements / Feature Requests | |
10min | IPAC | SUI / Level 3 and SuperTask feedback on the Butler | |
10min | SQUARE | ||
10min | NCSA |
| |
Architecture | Tim Jenness : I feel strongly that we should have two persistable file format options designed in to the butler (FITS and HDF5 say) so that we can be sure we have a flexible design that is not wedded to a single file format. |
Random notes
Butler (not-done) stories: