Page Comparison

Attendees:

• RAMPS: Stephen Deems (v), Dave Hart

• MATCH: Shelley Knuth (v), Alana Romanella

• CONECT: Tim Boerner (v), Leslie Froeschl

• MMS: Tom Furlani (v), Joe White

• RP: Jeremy Fischer

• OpenCI: John Towns (v), Shawn Strande, Amitava Majumdar, Lavanya Podila, Lisa Kaczmarczyk, Shannon Bradley

• NSF: Tom Gulbransen, Sharon Geva

• Guest Speaker:

(v) indicates a voting member

...

...

Date

...

Date

...

Decisions made during the meeting:

Agenda/Notes

1. Approval of summaries from prior EC meeting John Towns (5 mins)

   1. 2024-08-06 ACCESS EC Meeting Agenda & Summary

   2. None

2. EC Program Milestone Check John Towns (5 mins)

...

3. Update on “ACCESS Resources” Discussions (Deems)

• Resource Catalog - (in response to NSF asking for info more like a project plan last week)

  • Wireframes:

    • List View: https://drive.google.com/file/d/1_ob2y5jB37GvSg8yMKOdHv8lmxEJnb6t/view?usp=drive_link

    • Detailed View: https://drive.google.com/file/d/1RN5I3tvyLIdpYUIzQTOGi_V71-IvzJ1P/view?usp=drive_link

  • Draft of Implementation plan: https://docs.google.com/spreadsheets/d/1PS9uCenFk3QJxa8oUbajyqnvhRfbLyy5BBpHaXZFTtY/edit?gid=2012354515#gid=2012354515

  • Timeline

    • List of deliverables for V1 - (August 27)

    • Data curation (month of September)

    • Development (month of October)

    • Beta Testing with Staff and Users (November 1)

    • Launch - (Prior to 2025)

• Software Discovery

  • General Phases of Software Discovery

    • Data Collection, Curation, UI/UX

  • Path Forward

    • Operations team will handle the data curation (and repository)

      • Support team will utilize their data for the “missing” resources until data is made available

      • RPs may also have an option for how the data can be collected (pulled vs. pushed with installed tool)

    • Support team will re-design their existing system to pull from Operations APIs

    • Support team will combine and display the data to the community through their UI 

    • Vetting will be done in conjunction with RPs

• Resource “Selector”

  • In-depth discussions haven’t taken place in meetings, yet (due to topics above) but some next steps were presented through ad hoc meetings

  • Support is preparing to release a robust AI chatbot that can assist with a multitude of queries (including which resource may be best for a particular user)

    • Operations is willing to “retire” their AI chatbot if a better solution is available we can point to.

  • The screenshots from the above Resource Catalog can display helpful information to audiences about which resources are being used for what purpose/scientific domains

RPs will need to keep this updated going forward

• Can we get a commitment from the RPs to create a cadence to review this information?

• Could meetings with Operations or Support be updated to include the review?

• Put a time stamp on when the RPs included new information on the site? Jeremy says this idea could help

• We can also do emails and reminders from our side

• Leslie: this is being discussed during the RP Forum call this week to get their buy-in

• Could be part of Alana’s meetings with the RPs too

• It is not time to hide or move pages - but eventually it will all coalesce data sources into a single tool

• Tom F: In going along with Tim’s idea, perhaps we could have a Badge for this….they get a badge for a list that is up to date

• Could we put this on the Quarterly Meeting Schedule? Stephen says yes we could put some of the items on the agenda as an informative update
  

4. September Quarterly Meeting (Deems/Lavanya)

   1. Call for Agenda Topics

      1. Need more topics and more representation from teams.

         1. Where are the gaps?

      2. Lavanya sent out reminder this afternoon

      3. Once the topics deadline has passed (this Friday, August 16) the planning committee plans to send out a survey to staff to build further consensus on topics and provide staff an opportunity to share additional input.

   2. Misc.

      1. Working toward getting a shuttle from hotel to PSC offices and back

         1. Approximately 1 mile walk on flat ground (believe it or not)

      2. Will disseminate a list for others to enter their arrival/departure times to coordinate Uber/Lyft rides to/from the PIT airport. (not close to downtown)

      3. Eval group will be presenting metrics - they will be ready by then

Informational Items (10 mins)

Next EC Meeting: 21st August 2024

Action Tracker:

Format:

...

3. RP Forum Jeremy Fischer

4. Allocations Stephen Deems

   1. Attaching reports from current and previous Allocations Meetings (per request last meeting)

      1. Request List of upcoming September meeting

         1. ~3 are expected to be moved into the Accelerate ACCESS project type due to their size

      2. Results from March 2024 meeting

      3. Results from September 2023 meeting

   2. CLI Client that interacts with AMIE

      • Python tool for interacting with AMIE for small RPs 

      • We wouldn’t be doing usage reporting

   3. Profiles Update

      • When PIs go to create a project, they’ll be prompted for more information. 

      • Anyone that’s on a project will be notified periodically that they have missing data. 

5. MATCH Shelley Knuth/Alana

6. CONECT Tim Boerner/Leslie

7. MMS Tom Furlani

   1. Open XDMoD 11.0 in final testing and will be released soon

   2. REU students give presentations tomorrow

8. OpenCI John Towns

Misc Topics:

3. 1. Towns will be finalizing how the ACO responsibilities are handled in the “post-Shawn” era next week after return from PTO.

   2. Work on Tapia Conference is Ongoing

   3. Work on Quarterly meeting

   4. Work on integrated Milestone Tracking and gathering ideas on a How To Guide to use it

Misc Topics:

Lisa will be talking to the EC in two weeks to get EC feedback on what they are expecting from the Sept Quarterly Meeting - and how we can gather perceptions of value of an in person meeting

...

Action Tracker for EC Meetings:

...

Next EC Meeting: 20th August 2024

...

Reference:

Risk Register: https://access-ci.atlassian.net/jira/core/projects/RR/board

Project Change Request: https://access-ci.atlassian.net/jira/core/projects/PCR/board