You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The instrument team would like additional command line features, including:
capability of switching between different clustering and centroiding method
capability of skipping clustering step (show raw hits only, no clustering)
Su-Ann's inputs:
capability to save hits and events h5 files for SophireadStream with filename prefix related to the raw tpx3 filename [Optional]
capability to set the DSCALE as an optional user input [Optional]
capability to find a trustworthy tdc to get a proper tof [Optional]
moved DAS computing equipment to H-304 to be connected to MCP/TPX3 detector. This way, we can ssh into the server and use the detector.
DAS will share their whole repository with me and you so we can look into some of the issues that they’re facing. Just a pair of extra eyes, not obligated to do anything. They believe that the rate limitation they experienced comes from a layer before doing tpx3 parsing.
Once the detector is set up on network, I will be working with the vendor to figure out the timestamp issues (whether or not we should update the firmware, etc)
We weren’t able to test sophiread as much as we want. Once the detector is set up as it was at SNAP, we can test our software to make sure the display and tof is fixed, as well as check if the rate limitation can be solved with SophireadStream and other memory leak issues or bugs from Rick's code.
We need to discuss with DAS about software refactorization with documentations. First, read the repo they going to share, understand the resources we need in terms of servers (host documents) and prepare a plan to discuss/convince DAS to software refactoring efforts.
The text was updated successfully, but these errors were encountered:
The instrument team would like additional command line features, including:
Su-Ann's inputs:
capability to save hits and events h5 files for
SophireadStream
with filename prefix related to the raw tpx3 filename [Optional]capability to set the
DSCALE
as an optional user input [Optional]capability to find a trustworthy
tdc
to get a propertof
[Optional]moved DAS computing equipment to H-304 to be connected to MCP/TPX3 detector. This way, we can ssh into the server and use the detector.
DAS will share their whole repository with me and you so we can look into some of the issues that they’re facing. Just a pair of extra eyes, not obligated to do anything. They believe that the rate limitation they experienced comes from a layer before doing tpx3 parsing.
Once the detector is set up on network, I will be working with the vendor to figure out the timestamp issues (whether or not we should update the firmware, etc)
We weren’t able to test
sophiread
as much as we want. Once the detector is set up as it was at SNAP, we can test our software to make sure the display and tof is fixed, as well as check if the rate limitation can be solved withSophireadStream
and other memory leak issues or bugs from Rick's code.We need to discuss with DAS about software refactorization with documentations. First, read the repo they going to share, understand the resources we need in terms of servers (host documents) and prepare a plan to discuss/convince DAS to software refactoring efforts.
The text was updated successfully, but these errors were encountered: