-
Notifications
You must be signed in to change notification settings - Fork 18
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
SW-DES data location at the Zooniverse end #230
Comments
I already spoke to cam about this, as we cannot do it trough the project On Wednesday, 11 May 2016, Anupreeta [email protected] wrote:
|
yes, i remember that you mentioned something like that. but from the DES side, we would like to have more specific info for how to go about this if possible, so that we can begin setting things up in parallel to other tasks. |
tell me how many images you want for beta testing and i'll enquire On 12 May 2016, at 00:39, Anupreeta [email protected] wrote:
|
just to give you a number i'd say 500-1000 but we don't know yet for sure. also, for the beta sample, we can just use some ftp option but its good to have set things up and test with the beta sample already. thanks! |
Cam said this "Yeah, having the data on s3 and providing a CSV manifest (SRC URL, metadata) to us and we can import it. We can help with the s3 transfer too if needed" so should be straight forward. If we want randomised subject IDs in the metadata - we will need to take of that from our end before delivery - these will then given a subject Id int eh db of the form .e.g. 2056727. if we were to only people uploading at the time all the panoptest subject IDs would be sequential. e.g. one of the test data i just uploaded looks like |
Thanks @aprajita |
yes, s3 i think is the amazon data cloud On 17 May 2016 at 23:57, Anupreeta [email protected] wrote:
|
they can help with teh S3 transfer too |
Where and how to transfer the SW-DES beta data and then actual data for the launch?
For CFHTLS, we transferred the data to amazon servers using globus online interface.
The text was updated successfully, but these errors were encountered: