We continue to review all events currently planned for the next sixty days and organizers will be notified if their event must be canceled, postponed, or held remotely. Please, check back on Indico during this time for updates regarding your meeting specifics.
As DOE O 142.3A, Unclassified Foreign Visits and Assignments Program (FVA) applies not only to physical access to DOE sites, technologies, and equipment, but also information, all remote events hosted by Fermilab must comply with FVA requirements. This includes participant registration and agenda review. Please contact Melissa Ormond, FVA Manager, with any questions.
ZOOM meetings Lab policy:
You absolutely must not post Zoom meeting IDs on any public website
unless you set a password to protect the meeting/event.
Of course, do not post the password on any public website, either.
For details please refer to the news article https://news.fnal.gov/2020/05/security-guidelines-for-zoom-meetings-2/ Zoom information should be either given on email request or stored on a SharePoint page behind SSO".
Do NOT post the zoom information in the field 'Venue/Location' since it will show in the weekly Calendar even if the event is protected!
Indico search will be reestablished in the next version upgrade of the software: https://getindico.io/roadmap/
Dune data management meeting Aug 11 2020
Perfsonar will present at Monday ops meeting next week
Steve, Heidi, Kirby, Stu meeting with ESnet weekly, that is converging, first draft due this Friday,
This is what ESNet needs to build for DUNE and the short baseline neutrino program over the
Josh Klein DAQ performance Taskforce will schedule first meeting of DUNE metadata content.
Various dune data mgmt people have strong goal to keep as much as can be kept in the Runs DB and out of the metadata. Not clear if the Runs DB will get specified by the DB group unless
We push for it. Heidi volunteers to specify conditions that should be in the Runs DB and not in the metadata.. see below. Wenlong Yuan wants to participate at the level of being embedded in the DAQ group to make sure we get what we need and his Edinburgh management is OK with this.
There is also a question about how much of stuff from prptodune-SP that is in the metadata now should or could be moved to a runs DB instead of being brought forward into the new
Metadata server. Definitely do not want to repeat experience of protodune-sp in the second run of protodune where we were scraping google docs and ELISA notebooks to get values.
Meeting at 10AM today with T. Levshina, D. Litvinsev, M. Kirby, S. Timm, R. Illingworth to discuss DUNE storage layout for tokens.
Nicole Avila will present the work she has been doing next week.
Project planning overview
Metadata server requirements are stable, no comments.. but we will see if the metadata content meetings bring any unexpected requirements.
Igor, Steve, Robert, and Brandon working on sam project replacement scope and requirements doc, next meeting of this tomorrow.
After that we work on implementation plan.. some issues—can and should we bring all legacy data into Rucio, it’s not all there now, can and should we bring all the legacy metadata forward into the new metadata server. Need a very detailed plan with various decision points and a detailed punch list, Steve to lead.
We are trying to get a internal SCD review set up of the data management projects as well as the other big DUNE computing projects, (frameworks and DB) for this fall, presumably early fall after the collaboration meeting.. data mgmt projects should be ready to present at the collaboration meeting in late September whatever they will be showing there.
Will discuss in 2 weeks. Igor wants to participate in discussion with Heidi and Steve on what should go in it.
Naming contest for new sam project replacement