-
Notifications
You must be signed in to change notification settings - Fork 1
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
Automating file transfer off the FlowCam #20
Comments
@albags if this approach works in practise then it could leave us with different choices about data transfer We've discussed the different cases of reuse value for your work https://github.com/AMI-system/ami-api ("API to push data (images and audio files) into an S3 server.") - potentially seen as a backend for a GUI experience of small to medium sized image datasets In the internal Teams discussion the suggestion is that the transfer proxy could send the source images (in this case the collages before they are segmented) directly to cloud storage (JASMIN/s3) It still leaves the decollaging needing to run somewhere but at least detaches that from a named individual's on-premise virtual machine... |
From Microscope to Metadata talk from last year's RSECon - caveat, haven't watched and don't know if it has an image ML angle |
I've moved this into the TODO part of the backlog in the "Project" view after getting some feedback from Kelly in the lab - they're able to run Powershell commands in the CLI with administrator privilege - which seems very promising for setting up a scheduled task to do file transfer. It will need followup with @DamienUKCEH's team about possibility of using a transfer proxy with webhook from the FlowCam built-in PC. It's not an action til November, I've added it TODO so we remember to look at it then. |
Short summary of discussion with Science Computing folks, also relevant to #16
I've contacted Kelly in the lab to suggest a least-effort test of stage 2...
The text was updated successfully, but these errors were encountered: