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

Ref-based RNA-seq try to fix cyot default #3435

Closed
wants to merge 1 commit into from

Conversation

lldelisle
Copy link
Collaborator

@lldelisle lldelisle commented Apr 28, 2022

Hi,
I noticed a "bug" (at least a non expecting behaviour).

If you

  1. go to galaxy
  2. open the Ref-based tutorial
  3. go to the Counting the number of reads per annotated gene.
  4. Select the "STAR" flavour of the tutorial.
  5. Click outside of the box, go to 'view all histories', come back to your current history, open back the tutorial.
  6. It is back to the "featureCounts" flavour.

It seems that it stored the position where you were in the tutorial but not the choice.
This is probably what happened to: #989 (comment)
And this happened to us during the training.

The small fix I propose here is to use the URL but I don't know if there is a way to hide it behind the "STAR" button of the Choose your own tutorial. Also I am not sure it will work, is there a way to test?
@hexylena if you can help...

Thanks,

@lldelisle lldelisle requested a review from a team as a code owner April 28, 2022 07:12
@lldelisle lldelisle changed the title Ref--based RNA-seq try to fix cyot default Ref-based RNA-seq try to fix cyot default Apr 28, 2022
@hexylena
Copy link
Member

hexylena commented May 2, 2022

@bebatut will teach this next week, I will try and get this fixed in a more proper way before then

@lldelisle
Copy link
Collaborator Author

If she is teaching it with the featureCount flavour, she will probably not see any issue. The issue comes when we use the non-default tutorial.

@bebatut
Copy link
Member

bebatut commented May 2, 2022

Yes I will teach with default version

@hexylena
Copy link
Member

hexylena commented May 3, 2022

Fixing this in a more generic way in #3451

@hexylena hexylena closed this May 3, 2022
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.

None yet

3 participants