Analysis/Technical Note Submission
This page summarizes the procedure for submitting an analysis or technical note to the ePIC document repository. This is intended to be a simple, lightweight procedure that ensure that everyone relevant is informed when a new analysis or technical note is created.
Template for composing a note can be found on Zenodo: https://zenodo.org/records/16619274 and GitHub LINK
- Step 1: Collaborator contacts the Analysis/Technical/Software and Computing Coordination Office with title to receive note number
- Analysis/Technical/Software and Computing Coordination Offices maintain note numbers and list of notes
- Step 2: DSC/WG leadership signs off on note
- Work with DSC/WG leadership to identify the most appropriate DSC/WG
- Review should ensure the content of the note follows the standards of the collaboration and the results are accurate
- DSC/WG leadership sends an email to the Analysis/Technical/Software and Computing Coordinators to confirm
- Step 3: Collaborator submits to Zenodo
- Use keywords “ana_note” and “tech_note”, along with any other keywords that will make it easy to find the note efficiently. A list of official keywords is available here.
- Step 4: Analysis/Technical/Software and Computing Coordinators approve publishing to ePIC
- Analysis and Technical notes will be made available to ePIC Community members
The naming convention for ePIC analysis notes is “epic-[AN/TN]-[TC/SC/AC]-[Year]-[distinct number padded to 3 places]”. So the note “epic-TN-SC-2025-003” would be a technical note from Software and Computing first published as the third S&C note in 2025.