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

New IT blogpost added #2121

Merged
merged 10 commits into from
Sep 18, 2023
Merged

New IT blogpost added #2121

merged 10 commits into from
Sep 18, 2023

Conversation

tuncK
Copy link
Contributor

@tuncK tuncK commented Aug 15, 2023

Upon Sanjay's suggestion, I tried to write a new blogpost about interactive tools.


For a non-interactive tool execution, the user defines all inputs before the job execution and has access to the results after the job finishes. During the execution phase of the job, the user does not and cannot interact with the system. For majority of the scientific software, this model is actually sufficient, because they are commandline-only, the computation follows a pre-written recipe in the script and a user input during the computation is not needed at all.

<div align="center">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not getting rendered in the markdown. Have a look.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It gets rendered on my side. If you meant something else, please give more details.

image

content/blog/2023-08-15-ITs/index.md Outdated Show resolved Hide resolved
content/blog/2023-08-15-ITs/index.md Outdated Show resolved Hide resolved

## Updates from usegalaxy.eu

Within the four-year time window between September 2019 and August 2023, our public instance, [live.usegalaxy.eu](https://live.usegalaxy.eu), already had served 21 801 IT jobs executions. A coarse look into the job statistics suggests that the typical availability of the system was not very different than that of a user-owned local system. Thanks to the availability of VMs dedicated to IT executions in our cloud, users usually did not need to wait more than 30s after realising their need and spinning up an IT instance. This excludes the technical issues that we experienced in the recent past and now resolved, which meant we were unable to provide the resources within a few days.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Within the four-year time window between September 2019 and August 2023, our public instance, [live.usegalaxy.eu](https://live.usegalaxy.eu), already had served 21 801 IT jobs executions. A coarse look into the job statistics suggests that the typical availability of the system was not very different than that of a user-owned local system. Thanks to the availability of VMs dedicated to IT executions in our cloud, users usually did not need to wait more than 30s after realising their need and spinning up an IT instance. This excludes the technical issues that we experienced in the recent past and now resolved, which meant we were unable to provide the resources within a few days.
Within the four-year time window between September 2019 and August 2023, our public instance, [live.usegalaxy.eu](https://live.usegalaxy.eu), already had served 21801 IT jobs executions. A coarse look into the job statistics suggests that the typical availability of the system was not very different than that of a user-owned local system. Thanks to the availability of compute resources dedicated to IT executions in our cloud, users usually did not need to wait more than 30s after realising their need and spinning up an IT instance.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this This excludes the technical issues that we experienced in the recent past and now resolved, which meant we were unable to provide the resources within a few days because technical glitches and issues come and go.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I expressed during our conversation before, unless @bgruening overrules:

I want to keep the rightmost column in the graph (and a short argument explaining it to the attentive readers). Without backing with some orthogonal data, I think the outliers are part of a distribution. Transient glitches are part of our imperfect service quality. It functions pretty good nowadays, just that it did cause to some users at some point.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the figure and explanation.


## What are interactive tools (IT)?

For a non-interactive tool execution, the user defines all inputs before the job execution and has access to the results after the job finishes. During the execution phase of the job, the user does not and cannot interact with the system. For majority of the scientific software, this model is actually sufficient, because they are commandline-only, the computation follows a pre-written recipe in the script and a user input during the computation is not needed at all.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure this constitutes the only role of ITs. This is just an extra option/luxury that the users get.

For me IT's or VREs are more like the below:

ITs or VREs (Virtual research environments) provide researchers with digital spaces to conduct experiments, analyze data, and collaborate seamlessly. VREs such as Jupyter Notebook and Rstudio empower users with interactive coding environments, enabling real-time manipulation of code, visualizations, and data analysis and fostering iterative exploration. Thus, enhancing efficiency and reproducibility within these dynamic research landscapes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I blended this into the text, after a small adjustment to define VREs as a subset of ITs.

@sanjaysrikakulam
Copy link
Collaborator

I think it should be a news item. You might have to move it from blog to news.

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>
@tuncK
Copy link
Contributor Author

tuncK commented Aug 15, 2023

I think it should be a news item. You might have to move it from blog to news.

Moved as you suggested.

@tuncK tuncK requested a review from sanjaysrikakulam August 17, 2023 14:16
@tuncK
Copy link
Contributor Author

tuncK commented Sep 15, 2023

Hi @sanjaysrikakulam, as we discussed on Tuesday, I added sectioning, changed a few wordings and added the "steps to launch an IT" section as I mentioned. Any other issues that you notice?

Copy link
Collaborator

@sanjaysrikakulam sanjaysrikakulam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks great after the last changes. Thank you!

Copy link
Member

@bgruening bgruening left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @tuncK

@bgruening bgruening merged commit 5618461 into galaxyproject:master Sep 18, 2023
3 checks passed
paulzierep pushed a commit to paulzierep/galaxy-hub that referenced this pull request Nov 7, 2023
* IT blogpost added

* fixed broken link

* Update content/blog/2023-08-15-ITs/index.md

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>

* Update content/blog/2023-08-15-ITs/index.md

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>

* comments addressed

* relocate to news

* polished explanation regarding >200swaiting time

* sectioning and 4 step launch added

* fix broken URL

---------

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>
paulzierep pushed a commit to paulzierep/galaxy-hub that referenced this pull request Nov 28, 2023
* IT blogpost added

* fixed broken link

* Update content/blog/2023-08-15-ITs/index.md

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>

* Update content/blog/2023-08-15-ITs/index.md

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>

* comments addressed

* relocate to news

* polished explanation regarding >200swaiting time

* sectioning and 4 step launch added

* fix broken URL

---------

Co-authored-by: Sanjay Kumar Srikakulam <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants