Difference between revisions of "GettingStarted Software"

From Xem2
Jump to navigationJump to search
Line 16: Line 16:
 
*Communications about new features / calibrations / etc will be sent via the Software Slack channel.  Feel free to also watch Casey's repositories for email notifications.
 
*Communications about new features / calibrations / etc will be sent via the Software Slack channel.  Feel free to also watch Casey's repositories for email notifications.
  
'''Remember:''' The point of this scheme is for us to <font size="+0.5"><font color="Black">'''Collaborate'''</font></font>!  We can independently work on different calibrations / scripts / etc and bring all of our changes together to spread out the workload.
+
'''Remember:''' The point of this scheme is for us to <font size="+0.25"><font color="Black">'''Collaborate'''</font></font>!  We can independently work on different calibrations / scripts / etc and bring all of our changes together to spread out the workload.
  
== ==
+
==Hierarchy Visualization==
 +
[[Image:G4sbs_QtGUI.png|left|800px]]

Revision as of 00:35, 30 August 2021

Hall C Software for XEM2

We are using all standard equipment and thus the standard hall C analyzer (hcana).

Coding Paradigm

Resposibility

Prior to 2021, Abishek Karki replayed all the data for the XEM and F2 analyses. For all future passes of 2022 data, Casey Morean is in charge of maintaining the codebase.

Hierarchy

  • Git is used as version control for all shared code
  • Casey (https://github.com/mrcmor100) has forked from all relevant JeffersonLab (https://github.com/JeffersonLab) repositories
    • All XEM group members other than Casey only need to worry about changes to Casey's repositories.
    • Casey is in charge of pulling changes from the JeffersonLab repositories.
  • All XEM group members will 'Fork' Casey's repository, which will appear on their GitHub account, that is your 'origin'.
    • Changes can be made on a 'local' branch and then pushed to your 'origin'.
    • Once you have pushed your changes to your 'origin', you can make a pull request to Casey add your changes into 'upstream'.
  • Communications about new features / calibrations / etc will be sent via the Software Slack channel. Feel free to also watch Casey's repositories for email notifications.

Remember: The point of this scheme is for us to Collaborate! We can independently work on different calibrations / scripts / etc and bring all of our changes together to spread out the workload.

Hierarchy Visualization