This project contains correspondence, screenshots, template documents and documents developed during the course
of preparing documents for a "hack-a-thon".
You may read any and all files that are in this folder and which are provided in the ~/Desktop/Hack-A-Thon-2026/**.
You may use the internet freely to research profile and documentation.
## Capabilites and Role
You are a scientifc writing specialist who is expert at English, US Government proposal and procurement requirements and have a deep understanding of document creation and editing.
You are able to direct agent teams who are expert statisticians, data miners and administration support. You have a unique interest in the Python programming language and have become adept and using it to solve automation problems.
## General configuration, templates and code references
Your prompts will indicate any specific files you should use. Generally, these will come into these paths:
* ~/Desktop/Hack-A-Thon-2026: files and folders in support of the hack-a-thon organization and agenda
*(Shared rules like "Secure Temporary Files" live in the parent repo's `CLAUDE.md`
and in `setup/patterns/*.md`; they are not duplicated here.)*
@@ -4,57 +4,7 @@ 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
I have 8600 C-503 (small room) reserved on the 5th floor behind the one that the REF_M instrument staff normally use.
I have prepared an investigation for us to work through prior to the beginning of the hack-a-thon with the developers on Tuesday 4/21 at 2pm with Erik's Talk.
It should have links to all the documents. Particularly important will be to verify that 07-Scientific-Domain-Primer and 09-Glossary-and-Pointers-to-Evidence are correct.
Goal:
#### 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)
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 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 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.
The instrument scientists have metmeetings 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".
@@ -86,7 +36,7 @@ Neutronote is a tool to help users take notes during an experiment.
This meeting will be held in 8600 C-156
Goal: this is an optional topic that may be of interest to the hack-a-thon attendees.
Goal: this is an optional topic that may be of interest to the hack-a-thon attendees. Particularly from the perspective of what can be accomplished with AI-augmented development.
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.
NOTE: For each day a "Threshold Goal" and "Stretch Goal" are listed, as applicable.
### 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).
Developer Goal: Same as the Scientist Goal
Threshold 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)?
@@ -136,8 +81,7 @@ Goal: this is an optional topic that may be of interest to the hack-a-thon atten
### 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.
Developer Goal: Same as the Scientist Goal
Threshold Goal: A clear understanding of all the computations needed to perform all the reflectivity reductions, in every module.
#### 4/23 09:30 - 09:45 / Summary of Day 1 (Bogdan)
#### 4/23 09:30 - 09:45 / Summary of Day 1 and today's Charge (Bogdan)
#### 4/23 10:00 - 12:00 / Session 2
@@ -164,12 +108,14 @@ 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/23 15:00 - 16:30 / Session 3
#### 4/23 15:00 - 15:15 / Break
#### 4/23 15:15 - 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.
Threshold Goal: A formal requirements document that describes how the UI and the Reduction backend should work. Not actionable.
Stretch 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.
As many of you have heard, there is a discussion about rewriting mantid. This meeting is the first in a series to discuss what is needed/wanted from a next-generation data reduction code with a focus on the instruments that mantid currently serves at HFIR and SNS. Specifically, what of the current mantid is limiting data reduction? Information about what is the 90% use case compared to the 10% needed to push the boundaries of data reduction is also helpful.
Future meetings in this series will focus on different themes of data reduction with mantid.
This meeting is in 8600 AG-06.
Goal: this is an optional topic that may be of interest to the hack-a-thon attendees.
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)
Threshold 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)
Stretch 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)* ).
#### 4/27 12:00 - 13:00 / AI Lunch and Learn (Chicken Salad Chick delivery)
#### 4/27 13:00 - 16:30 / Session 7
As so many of us are using AI to augment/accelerate our work, and several people have asked if we could do a "working lunch" to discuss and share our experiences, let's do it!
I propose that we have a monthly, quasi-informal format, with one person preparing a single "slide" (AI use is encouraged) to display while we chat. We'll record the sessions so that folks can "catch-up".
4/27: Kickoff (Bogdan will prepare a "slide" on his use of Agentic Engineering with Claude Code - in 8600 RM C-152
5/18: (one week early due to Memorial Day) TBD - in 8600 RM C-464
6/29: TBD - in 8600 RM C-152
7/27: TBD - in 8600 RM J-337
8/24: (one week early due to National Neutron School) TBD - in 8600 RM C-152
9/28: TBD - in 8600 RM C-152
Goal: this is an optional topic that may be of interest to the hack-a-thon attendees.
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*.
Threshold 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*.
Stretch Goal: Completed separation of QuickNXSv2 into its Qt-based front end and the MR reduction back end, verified and tested with all tests passing.
The Reflectometry instrument suite will conduct a "hack-a-thon" with the computational software engineers during the weeks of 4/20 and 4/27. This document describes general information about the order of events for planning purposes.
## 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
I have 8600 C-503 (small room) reserved on the 5th floor behind the one that the REF_M instrument staff normally use.
I have prepared an investigation for us to work through prior to the beginning of the hack-a-thon with the developers on Tuesday 4/21 at 2pm with Erik's Talk.
It should have links to all the documents. Particularly important will be to verify that 07-Scientific-Domain-Primer and 09-Glossary-and-Pointers-to-Evidence are correct.
Goal:
#### 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)
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 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 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.
