@@ -5,13 +5,17 @@ The Reflectometry instrument suite will conduct a "hack-a-thon" with the computa
## Pre-Hack-A-Thon Meetings
The instrument scientists will have meetings on the days prior to the "hack-a-thon" to organize their position and requests so as to have clarify goals and desired outcomes for the "hack-a-thon".
### 4/20 13:00 - 16:00 / General Planning (w/coffee break) for Instrument
#### 4/20 13:00 - 16:00 / General Planning (w/coffee break) for Instrument
I have 8600 C-503 (small room) reserved on the 5th floor behind the one that the REF_M instrument staff normally use.
@@ -23,27 +27,27 @@ It should have links to all the documents. Particularly important will be to v
Goal:
### 4/21 09:30 - 10:00 / Daily Status - Neutrons with the computational softare engineers (optional)
#### 4/21 09:30 - 10:00 / Daily Status - Neutrons with the computational software engineers (optional)
The software engineers meet in 8600 C-464 for a daily report on their progress. This is not hack-a-thon specific.
### 4/21 10:00 - 11:00 / Software and Coffee (optional)
#### 4/21 10:00 - 11:00 / Software and Coffee (optional)
This is a recurring meeting to discuss reduction software issues. That room is not available this week.
This is a recurring meeting nomally in 8600 C-502 to discuss reduction software issues. That room is not available this week. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a recurring meeting in 8600 C-248 to discuss reduction software issues specifically for BL4B. The room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a recurring meeting normally in 8600 C-248 to discuss reduction software issues specifically for BL4B. The room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a recurring meeting in 8600 J-337 to discuss instrument specific aspects. The room is tentative due to the SRC meeting.
This is a recurring meeting normally in 8600 J-337 to discuss instrument specific aspects. That room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
Goal: This is a recurring meeting for REF_L staff, it is optional for hack-a-thon attendees.
### 4/21 14:00 - 15:00 / LiqRef Presentation by Erik Watkins
### Day PRE2 (4/21 14:00 - 4/21 16:30)
Prior to the "hack-a-thon" proper, two activities of a preparatory nature will occur. One is mandatory the other is optional for the hack-a-thon participants.
#### 4/21 14:00 - 15:00 / LiqRef Presentation by Erik Watkins
The combined team (which includes the attendee list below) gathers for a kick-off presentation by Erik Watkins on reflectometry basics and the physics and math behind the reduction and analysis software.
NOTE: For each day a "Scientist Goal" and "Developer Goal" are listed. This is because currently there exists a 'schism' between the Scientist and the Developers (as observed from conversations from the last planning meeting on 4/10). The amount of work and the outcomes are currently very different, and these need to be reconciled.
### Day 1 (4/22 09:30 - 16:30)
Scientist Goal: Assessment and Agreement of whether QuickNXS V2 is or is not conducive for refactoring/modularization into "front-end" UI components and "back-end" reduction via [mr_reduction](https://github.com/neutrons/MagnetismReflectometer).
This is a recurring meeting normally held in 8600 C-502 to discuss reduction software issues specifically for BL4A. The room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a meeting in which people are discussing an alternative to Mantid called pyNEX. It was supposed to be held in 8600 J-337 but the room has been declined and they may be looking for a meeting room. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a meeting in which people are discussing an alternative to Mantid called [pyNEX](https://code.ornl.gov/nscd-neutron-instrument-development/pynex). It was supposed to be held in 8600 J-337 but the room has been declined and they may be looking for a meeting room. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
Goal: this is an optional topic that may be of interest to the hack-a-thon attendees.
### 4/23 09:30 - 16:30
### Day 2 (4/23 09:30 - 16:30)
Scientist Goal: A clear understanding of all the computations needed to perform all the reflectivity reductions, in every module, and what "correct" reduction is.
This is a recurring meeting in 8600 J-337 to discuss instrument specific aspects. The room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
This is a recurring meeting normally in 8600 C-502 to discuss instrument specific aspects. The room is tentative due to the SRC meeting. Perhaps our hack-a-thon may host the discussion as part of its agenda (to be discussed)?
Goal: This is a recurring meeting for REF_M staff, it is optional for hack-a-thon attendees.
Maria Patrou will present the Model-View-Presenter design pattern.
This presentation is part of the hack-a-thon and is in the room of the day: 8610 L-183.
### 4/24 09:30 - 16:30
#### 4/23 15:00 - 16:30 / Session 3
### Day 3 (4/24 09:30 - 16:30)
Scientist Goal: An actionable plan for what components and computation are needed to be in the "back-end", what components and calls will be used (based on existing usage), no duplication of functions.
Developer Goal: A formal requirements document that describes how the UI and the Reduction backend should work. Not actionable.
#### 4/24 09:30 - 09:45 / Summary of Day 2 (Bogdan)
#### 4/23 10:00 - 12:00 / Session 4
#### 4/24 12:00 - 13:00 / Lunch (Pizza Delievery)
#### 4/24 13:00 - 16:30 / Session 5
### Day 4 (4/27 09:30 - 16:30)
Scientist Goal: Code review of Agentic AI development artifacts ( *performed via the actionable plan generated by COB Day 3, and executed according to the model proposed by [this document](https://code.ornl.gov/6ov/tasking/-/blob/lr_reduction-new_workflow-repairs/plan/lr_reduction-new_workflow-repairs-plan.md?ref_type=heads)* ).
Developer Goal: Generation of Tickets in the [EWM Neutron Data Project (Change Management) System](https://ornlrse.clm.ibmcloud.com/ccm/web/projects/Neutron%20Data%20Project%20(Change%20Management)#action=com.ibm.team.dashboard.viewDashboard)
Scientist Goal: Completed separation of QuickNXSv2 into its Qt-based front end and the MR reduction back end, verified and tested with all tests passing.
Developer Goal: Triage and Estimation of the EWM tickets generated by COB Day 4. Agreement on the expected timeline and schedule to *perform the separation of QuickNXSv2 into its Qt-based front end and the MR reduction back end*.
