Difference between revisions of "EPSCI Group Meeting Aug. 24, 2020"

From epsciwiki
Jump to navigation Jump to search
 
Line 64: Line 64:
 
<hr>
 
<hr>
 
=== Minutes: ===
 
=== Minutes: ===
−
<!-- Attendees: David L.(chair), Carl T., Nathan B., Thomas B., Vardan G., Kishan R., Graham H.->
+
Attendees: David L., Carl T., Nathan B., Thomas B., Vardan G., Kishan R., Graham H.
 +
 
 +
 
 +
'''Code Reviews/Fortnight Papers'''
 +
* Our first dedicated Code Review/Fortnight Paper meeting will be next week.
 +
* Nathan will provide the first example code for code review. He will send it around sometime Wed.
 +
 
 +
'''Coding Standards'''
 +
* We continued the discussion on coding standards from last week
 +
* Vardan noted the main thing we'd like to accomplish is a common style and this is usually achieved via IDE
 +
* Google has some popular standards that may be worth looking at
 +
** Nathan noted at one point their C++ standards forbid use of exceptions (which we agreed was not something we would want)
 +
* Kishan noted the Python authors promote a set of standards for python
 +
* Vardan, Nathan, and Kishan will continue looking into Java, C++, and Python respectively
 +
** They will send around e-mails sometime over the next 2 weeks so we can move the discussion offline where people have more time to look into the suggestions.
 +
 
 +
'''EVIO-6'''
 +
* Testing of C++ port continues
 +
* Nathan has started looking into code and will communicate his thoughts to Carl
 +
* Carl is making progress on completing the project
 +
 
 +
'''SPACK'''
 +
* Not much recent progress.
 +
* Thomas is in communication with Wouter and anticipates moving things from the EIC-spack implementation to ours once ours is in place.
 +
* David noted that Bob Michaels provided a list of the tests he does when building a new version of ROOT. They are fairly extensive.
 +
** Not clear there is a testing mechanism in SPACK itself so we may need to add this ourselves.
 +
 
 +
'''ERSAP'''
 +
* Vardan continues working on Data Lake design
 +
** Studying different configurations with redis
 +
* Using Chris L.'s stream source for tests
 +
* Plans to test 3 more software options after Redis testing completes
 +
* Tests being done on indras3 (2TB memory)
 +
* Dave A. and Ben working on hardware setup in Indra lab that should be available next week.
 +
 
 +
'''JANA2'''
 +
* Nathan has begun working again on the GlueX port and has been converting factories that don't depend on JGeometry
 +
* Work has been done on the A.I. task support system. Close to ready for Kishan to start testing.
 +
 
 +
''' A.I.'''
 +
* Looking into C++ and Tensorflow
 +
** No native C++ interface, only C
 +
** Some 3rd party packages out there, but nothing that looks like a completed community standard
 +
* Found path for saving models trained in python to be read in using Tensorflow-C.
 +
** Will provide simple python routine for users
 +
* Kishan will add a page to the EPSCI wiki with instructions for using the sciml nodes
 +
* Thomas noted a report from Alex A. of Hall-D who was trying to use a sciml node for amplitude analysis and found issues if others were running python there.
 +
** More investigation is needed to determine if this is due to system configuration, or users.
 +
 
 +
'''OSG'''
 +
* Several OSG upgrade projects basically at the finish line
 +
* Update meeting is planned for Wed. that Thomas will attend.
 +
* Some discussions with Richard J. at UCon about moving the GlueX collect from there to JLab with UConn serving as the backup.
 +
 
 +
'''Offsite Processin'''
 +
* GlueX Spring 2020 data is now being processed offsite at both NERSC and PSC
 +
* NERSC throughput is minimal. PSC a little better
 +
* Occasional problems require Chris L. to reset something to get jobs moving again.
 +
* David needs to write up documentation so day-to-day can be handed over to Hall-D postdoc.

Latest revision as of 20:49, 24 August 2020

The meeting time is 10:00am.

Connection Info:

You can connect using BlueJeans Video conferencing (ID: 253 300 597). (Click "Expand" to the right for details -->): 

Meeting URL
 https://bluejeans.com/253300597?src=join_info

Meeting ID
253 300 597

Want to dial in from a phone?

Dial one of the following numbers:
+1.888.240.2560 (US Toll Free)
(see all numbers - https://www.bluejeans.com/premium-numbers)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

Agenda:

  1. Previous meeting
  2. Announcements
  3. Graham's Project
  4. Ongoing Activities
  5. GUI for Calorimeter calibration scripts (Hall-D Request)
  6. Publications
  7. AOT


Minutes:

Attendees: David L., Carl T., Nathan B., Thomas B., Vardan G., Kishan R., Graham H.


Code Reviews/Fortnight Papers

  • Our first dedicated Code Review/Fortnight Paper meeting will be next week.
  • Nathan will provide the first example code for code review. He will send it around sometime Wed.

Coding Standards

  • We continued the discussion on coding standards from last week
  • Vardan noted the main thing we'd like to accomplish is a common style and this is usually achieved via IDE
  • Google has some popular standards that may be worth looking at
    • Nathan noted at one point their C++ standards forbid use of exceptions (which we agreed was not something we would want)
  • Kishan noted the Python authors promote a set of standards for python
  • Vardan, Nathan, and Kishan will continue looking into Java, C++, and Python respectively
    • They will send around e-mails sometime over the next 2 weeks so we can move the discussion offline where people have more time to look into the suggestions.

EVIO-6

  • Testing of C++ port continues
  • Nathan has started looking into code and will communicate his thoughts to Carl
  • Carl is making progress on completing the project

SPACK

  • Not much recent progress.
  • Thomas is in communication with Wouter and anticipates moving things from the EIC-spack implementation to ours once ours is in place.
  • David noted that Bob Michaels provided a list of the tests he does when building a new version of ROOT. They are fairly extensive.
    • Not clear there is a testing mechanism in SPACK itself so we may need to add this ourselves.

ERSAP

  • Vardan continues working on Data Lake design
    • Studying different configurations with redis
  • Using Chris L.'s stream source for tests
  • Plans to test 3 more software options after Redis testing completes
  • Tests being done on indras3 (2TB memory)
  • Dave A. and Ben working on hardware setup in Indra lab that should be available next week.

JANA2

  • Nathan has begun working again on the GlueX port and has been converting factories that don't depend on JGeometry
  • Work has been done on the A.I. task support system. Close to ready for Kishan to start testing.

A.I.

  • Looking into C++ and Tensorflow
    • No native C++ interface, only C
    • Some 3rd party packages out there, but nothing that looks like a completed community standard
  • Found path for saving models trained in python to be read in using Tensorflow-C.
    • Will provide simple python routine for users
  • Kishan will add a page to the EPSCI wiki with instructions for using the sciml nodes
  • Thomas noted a report from Alex A. of Hall-D who was trying to use a sciml node for amplitude analysis and found issues if others were running python there.
    • More investigation is needed to determine if this is due to system configuration, or users.

OSG

  • Several OSG upgrade projects basically at the finish line
  • Update meeting is planned for Wed. that Thomas will attend.
  • Some discussions with Richard J. at UCon about moving the GlueX collect from there to JLab with UConn serving as the backup.

Offsite Processin

  • GlueX Spring 2020 data is now being processed offsite at both NERSC and PSC
  • NERSC throughput is minimal. PSC a little better
  • Occasional problems require Chris L. to reset something to get jobs moving again.
  • David needs to write up documentation so day-to-day can be handed over to Hall-D postdoc.
Retrieved from "https://wiki.jlab.org/epsciwiki/index.php?title=EPSCI_Group_Meeting_Aug._24,_2020&oldid=279"