Warning, /epic.github.io/_documents/note_process.md is written in an unsupported language. File is not indexed.
0001 ---
0002 title: Analysis/Technical Note Submission
0003 name: note_process
0004 layout: default
0005 ---
0006 {% include layouts/title.md %}
0007
0008 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.
0009
0010 * **Step 1**: Collaborator contacts the Analysis/Technical/Software and Computing Coordination Office with title to receive note number
0011 * Analysis/Technical/Software and Computing Coordination Offices maintain note numbers and list of notes
0012 * **Step 2**: DSC/WG leadership signs off on note
0013 * Work with DSC/WG leadership to identify the most appropriate DSC/WG
0014 * Review should ensure the content of the note follows the standards of the collaboration and the results are accurate
0015 * DSC/WG leadership sends an email to the Analysis/Technical/Software and Computing Coordinators to confirm
0016 * **Step 3**: Collaborator submits to Zenodo
0017 * 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.](/documents/keywords)
0018 * **Step 4**: Analysis/Technical/Software and Computing Coordinators approve publishing to ePIC
0019 * Analysis and Technical notes will be made available to ePIC Community members
0020
0021
0022 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.
