Skip to content

Conversation

@d-chambers
Copy link
Contributor

@d-chambers d-chambers commented Oct 4, 2024

Description

This PR adds support for a Neubrex DAS file which was shared from a student at CSM. Unfortunately, it is entirely different from the Neubrex DTS/DSS support we implemented in #411, but simple enough to support.

Checklist

I have (if applicable):

  • referenced the GitHub issue this PR closes.
  • documented the new feature with docstrings or appropriate doc page.
  • included a test. See testing guidelines.
  • your name has been added to the contributors page (docs/contributors.md).
  • added the "ready_for_review" tag once the PR is ready to be reviewed.

@d-chambers d-chambers added IO Work for reading/writing different formats ready_for_review PR is ready for review labels Oct 4, 2024
@codecov
Copy link

codecov bot commented Oct 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.85%. Comparing base (c045e6e) to head (24a8bb5).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #445   +/-   ##
=======================================
  Coverage   99.84%   99.85%           
=======================================
  Files         114      115    +1     
  Lines        9258     9337   +79     
=======================================
+ Hits         9244     9323   +79     
  Misses         14       14           
Flag Coverage Δ
unittests 99.85% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@ahmadtourei ahmadtourei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! One general suggestion: it would be beneficial to enhance the class naming conventions in the IO module down the road as we're expanding IO capabilities to DSS and DTS formats. This would be particularly useful in the homepage documentation helping users quickly know if their data type/format of interest is implemented.

@d-chambers
Copy link
Contributor Author

Looks great! One general suggestion: it would be beneficial to enhance the class naming conventions in the IO module down the road as we're expanding IO capabilities to DSS and DTS formats. This would be particularly useful in the homepage documentation helping users quickly know if their data type/format of interest is implemented.

Yes, this is probably a good idea. However, from what I can tell, the other Neubrex file format (currently used for DSS and DTS at forge) would have worked just fine for DAS data as well. I am not 100% sure if they have different formats for DAS and DTS or maybe they just have different formats that are sometimes used for either, or maybe they are just different versions of the same format?

I really wish everyone would include a name of the file format and a version code in the headers so we don't have to guess at these things.

I am dragging my feet a bit on merging this until I have some more time to think about it. If anyone knows someone at Neubrex that would be willing to help us figure out the best approach here that would be useful.

@arturguzik
Copy link

Derrick, I'm about to respond to you over mail, with comments on our (Neubrex) format. Both RFS and DAS.

@d-chambers
Copy link
Contributor Author

Hi @arturguzik, I got your email. I will take a closer look in the next few days and get back to you if I have any questions. Thanks in advance for the help.

@d-chambers d-chambers merged commit e30d96d into master Nov 6, 2024
@d-chambers d-chambers deleted the neubrex_das branch November 6, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

IO Work for reading/writing different formats ready_for_review PR is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants