Date & Time 

  11:00 PDT

Location

Browser

Room System

Phone Dial-in

https://bluejeans.com/927260081

  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 103664856 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 927260081

Attendees

Regrets

Discussion items

Note that this is a special DM-SST meeting focsed only on the Gen3 Acceptance testing. DM-SST members who are not concerned with this topic are excused. Similarly non DM-SST members who are interested are invited to participate

 ​

ItemWhoPre-Meeting NotesNotes and  Action Items
Gen 3 middleware acceptance test campaign

Leanne Guy Jeffrey Carlin Jim Bosch 

Summary:

feature-complete: 81
mostly-implemented: 1
feature-incomplete: 25
unclear: 14
hackable: 2
needs-service: 2 Total: 126

  • LPG: What do unclear, hackable and need-service mean?
  • JB:  
    • unclear: any of: ground has shifted / don't understand requirements / how should the original use case be satisfied.  Review needed. 
    • hackable: low level codein place in middleware and could be satisfied by writing a script,  but the intention of the original requirement envisaged higher-level functionality, which this might not be necessary or worth the effort. 
    • needs-service:satisfying the requirement not on the mw itsefl but on an associated service. Maybe better tested via the associated service. 
  • LPG: Requirement review needed for the above categories. Which are priorities for the near term. hacakble/ needs-service seem low priority to resolve.  Set up a PR to review offline. Those that are still unclear after internal review will go to the DM-SST vF2F meeting. 
  • CTS: unclear are more ancillary requirements, i.e  not driving needs.
  • JB: We want to resolve early for architecture concerns. 
  • LPG: Does feature-incomplete imply not started? 
  • JB: Not necessarily, could mean 'not-started'.
  • JB: Some feature-complete require non-trivial test cases. The ones listed in the comments tabs are those that are  easy  Include harder ones in the next acceptance test  campaign. Some would be better done with a DR.
  • About 15 that we can easily do with ci_hsc. Others involve transfers from the RSP.
  • TJ: No explicit test case that we can do everything G2 does. We don't have a test case for refcat ingest.  
  • CTS: There are no requirement on refcats.
  • LPG: Will not include refcat ingest testing in this milestone. Will consider this as part of a future test campaign. We will need to do this at somepoint. 
  • TJ: Concerned that  we are not staring from an empty Gen3 repo and populating it for any of these tests. In future we should plan to start from an empty repo, ingest, process, analyse data. ci_hsc_gen3 was created from Gen2.  No test should start from G2 and convert. All test must be fully G3 (end-to-end, empty repo to processed visits) native testing.  
  • LPG: This is important ot test but not for this specific milestone. Add a note for future campaigns. (i.e in the test report)
  • JB: Mini-rc2 - talk to Brock and get his configuration files to run 
  • CTS: Many requirements are things that ci_hsc does. Do we need to write extra code? 
  • TJ: Can we point to the X lines of unit test code?  Weekly tag code. Name the test method in the test script - e.g functionality X in tag Y tests Z. Not just lists of lines of code 
  • LPG: yes 
  • JB : Add requirement IDs to the unit test code. Jim would just spend a day doing this.
  • JB: On test script is to just run ci_hsc. 
  • JC: Let's create one LVV-T per unit test. 

Actions: 

  • Leanne Guy Request Austin load up the mv requirements.  
  • Jeffrey Carlin Leanne Guy Map imported requirements to test cases following Jim's comments in each test case.  
  • Jim Bosch Analyze unit tests, annotate with associated requirements that can be covered by the test  
  • Jim Bosch Make PR for requirements review  
  • Jeffrey Carlin Point Jim to Jira location to add notes on code to run  



AOB

Leanne Guy

Next meeting is   



List of SST tasks (Confluence)

DescriptionDue dateAssigneeTask appears on
  • Robert Lupton Clarify the meaning of time in the object table. 1 sentence description in sdm_schemas, can link to a short DMTN.  Update 2022-02-09: Meeting to resolve this on 2022-02-21  
28 Feb 2022Robert Lupton2018-11-05 DM SST F2F Agenda and Meeting notes
  • Gregory Dubois-Felsmann check if SDM standardization is adequately represented in project documents, and whether DMTN-067 should be required.
31 Mar 2022Gregory Dubois-Felsmann2022-02-14 DM-SST Virtual F2F Agenda and Meeting notes
28 Feb 2023Leanne Guy2023-01-23 DM-SST Agenda and Meeting Notes
  • Leanne Guy talk to Steve R about presenting plans for the ShearObject table to PST and SciCollab chairs   
20 Mar 2023Leanne Guy2023-02-27 DM-SST Agenda and Meeting Notes
31 Mar 2023Jim Bosch2023-02-27 DM-SST Agenda and Meeting Notes
  • Leanne Guy  talk to Gregory Dubois-Felsmann to review the original intent of the AFS-related Portal requirements before deciding on a course of action  
29 May 2023Leanne Guy2023-05-01 DM-SST Focus Meeting - Brokers in Commissioning
  • Leanne Guy Prepare to consult the PST on the question of providing compressed PVIs for AP outputs, to cover the period before the data become available in a DR.  
02 Jun 2023Leanne Guy2023-03-27 DM-SST Agenda and Meeting Notes
  • Jim Bosch Incorporate 30-60 day period for raws on disk into the strawman proposal and present to KT  
26 Jun 2023Jim Bosch2023-05-08 DM-SST Agenda and Meeting Notes
  • Parker Fagrelius Patrick Ingraham  how long will it take to do a scan as described? No need to scan the whole WL range but will require additional points outside nominal lambda range.  
30 Jun 2023Parker Fagrelius2023-03-27 DM-SST Agenda and Meeting Notes
31 Jul 2023Colin Slater2023-07-10 DM-SST Agenda and Meeting Notes
  • Eli Rykoff , Leanne Guy  Develop a proposal for what calibration processing, hardware, data we actually need and what will be needed for DR1. This has implications for the ORR and for prioritisation of work in commissioning  
31 Jul 2023Eli Rykoff2023-01-30 DM-SST Agenda and Meeting Notes
  • Yusra AlSayyad will look to see if there is any effort to help on option 1  
28 Aug 2023Yusra AlSayyad2023-08-14 DM-SST Agenda and Meeting Notes
  • Jim Bosch  Provide a physical example of that a  up on cell table would look like fo the Colin Slater / DAX team to review  
31 Aug 2023Jim Bosch2023-02-27 DM-SST Agenda and Meeting Notes
  •  "What is the pathway to defining the data products that are required to meet DMS-REQ-0266" Jeffrey Carlin   
30 Nov 2023Jeffrey Carlin2023-10-23 DM-SST vF2F Agenda and Meeting Notes
30 Nov 2023Gregory Dubois-Felsmann2023-10-23 DM-SST vF2F Agenda and Meeting Notes
30 Nov 2023Leanne Guy2023-10-23 DM-SST vF2F Agenda and Meeting Notes
  • Jeffrey Carlin follow up with KT on DMS-REQ-0176 and DMS-REQ-0315 to update/disaggregate this for latest base/summit infrastructure split.  
30 Nov 2023Jeffrey Carlin2023-10-23 DM-SST vF2F Agenda and Meeting Notes
  • Jim Bosch Follow up on the possibility of investigating further the ability to process 2 collections in parallel.   
31 Jan 2024Jim Bosch2023-12-04 DM-SST Agenda and Meeting Notes
31 Jan 2024Jeffrey Carlin2023-12-04 DM-SST Agenda and Meeting Notes
Gregory Dubois-Felsmann2023-10-23 DM-SST vF2F Agenda and Meeting Notes