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
Users need to register manually curated spike data. The registration could be done in ibllib by registering to an 3S instance mounted to an EC2 instance running Globus. Alyx could then handle the transfers however something needs to assert that no Flatiron data are overwritten by this S3 data.
This issue is for simply determining the best course of action:
Confirm S3 can allow CREATE without DELETE
Determine whether possible to create an Globus ID from an S3 bucket (may need to ask SDSC)
Determine whether to use Alyx Globus management command and/or to run S3 sync from SDSC
The text was updated successfully, but these errors were encountered:
Step 1: Run from local server of AWS instance
Run a task using the s3 patcher
Check out s3_patcher branch of ibllib
Run a task with location='EC2', e.g
task = SpikeSorting(session_path, one=one, location='EC2', **kwargs)
task.run()
# This will upload the files via the s3 patcher to the [s3 patcher bucket](https://us-east-1.console.aws.amazon.com/s3/buckets/s3-patcher?prefix=patcher/®ion=us-east-1&bucketType=general)
task.register_datasets()
Step 2: Run from SDSC
Launch the sync script from the patcher to flatiron
Checkout s3_patcher branch of iblalyx on SDSC
Run the following
Users need to register manually curated spike data. The registration could be done in ibllib by registering to an 3S instance mounted to an EC2 instance running Globus. Alyx could then handle the transfers however something needs to assert that no Flatiron data are overwritten by this S3 data.
This issue is for simply determining the best course of action:
The text was updated successfully, but these errors were encountered: