-
Notifications
You must be signed in to change notification settings - Fork 0
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
Compute and Transfer Example Flows #1
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Ada <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm leaving initial feedback about the names and descriptions for a number of items. I'll come back to review the Python/JSON code after you've had a chance to review/respond. 👍
compute_transfer_examples/compute_transfer_example_1_definition.json
Outdated
Show resolved
Hide resolved
|
||
and save the Compute function's UUID. | ||
|
||
**Important**: Use the same Python version for registration as the one running on your Globus Compute Endpoint. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an easy way to verify the remote python version via the CLI? If so, might be helpful to show a CLI snippet here as an example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After thinking about it for a bit, adding this would mean diving into the globus-compute-endpoint
CLI which is then encroaching on the territory of the linked tutorial for endpoint setup in 'Prerequisites'. Unless you have strong feelings about this, I'm inclined to leave it as is.
Created two example Compute and Transfer flows and a script to register the Compute function both examples invoke.