Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid creating copy of the original nwb file at insert #1104

Open
5 tasks
samuelbray32 opened this issue Sep 11, 2024 · 0 comments
Open
5 tasks

Avoid creating copy of the original nwb file at insert #1104

samuelbray32 opened this issue Sep 11, 2024 · 0 comments
Labels
Database Issues with Frank Lab database, not Spyglass code enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users

Comments

@samuelbray32
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

  • Currently, sgi.insert_sessions() makes a copy of the nwb file with external link objects back to the original for large data items (e.g. electric series)
    • Was originally done to enable moving the original large file off the filesystem once intitial analysis completed
    • With fetch_nwb now able to access files on Dandi, no longer need the stand-in copy to enable moving big raw files off filesystem
  • We should instead use the original nwbfile in place of the copy
  • This shouldn't cause any noticable change to user's data access steps

Steps to implement

  • Move the raw nwb file to be named the same as the underscore file, deleting the underscore file
  • Edit the file database to update the checksum / size information for the file in the database
  • Update the code to stop making the underscore copy during insert.
  • Update the Import tutorial.
  • Check spyglass where the naming system is assumed
@samuelbray32 samuelbray32 added enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users Database Issues with Frank Lab database, not Spyglass code labels Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Database Issues with Frank Lab database, not Spyglass code enhancement New feature or request infrastructure Unix, MySQL, etc. settings/issues impacting users
Projects
None yet
Development

No branches or pull requests

1 participant