Skip to content

Commit 1f4d664

Browse files
committed
updates for Part 2
1 parent 8d32efe commit 1f4d664

File tree

5 files changed

+30
-22
lines changed

5 files changed

+30
-22
lines changed
94.4 KB
Loading
53.9 KB
Loading
37.8 KB
Loading
22.3 KB
Loading

topics/introduction/tutorials/galaxy-intro-peaks2genes/tutorial.md

Lines changed: 30 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,13 @@ contributions:
4040
- deNBI
4141
- uni-freiburg
4242

43+
answer_histories:
44+
- label: "usegalaxy.eu"
45+
history: https://usegalaxy.eu/u/teresa-m/h/gtn-peaks-to-genes-introduction-part-1
46+
date: 2025-08-19
47+
- label: "usegalaxy.eu"
48+
history: https://usegalaxy.eu/u/teresa-m/h/gtn-peaks-to-genes-introduction-part-2
49+
date: 2025-08-19
4350
---
4451

4552
We stumbled upon a paper ({% cite Li2012 %}) called *"The histone acetyltransferase MOF is a key regulator of the embryonic stem cell core transcriptional network"*. The paper contains the analysis of possible target genes of an interesting protein called Mof. The targets were obtained by ChIP-seq in mice and the raw data is available through [GEO](https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE37268).
@@ -195,14 +202,14 @@ we also need a list of genes in mice, which we can obtain from UCSC.
195202
> ![UCSC table browser interface](../../images/intro_02.png)
196203
>
197204
> 3. Set the following options:
198-
> - *"clade"*: `Mammal`
199-
> - *"genome"*: `Mouse`
200-
> - *"assembly"*: `July 2007 (NCBI37/mm9)`
201-
> - *"group"*: `Genes and Gene Predictions`
202-
> - *"track"*: `RefSeq Genes`
203-
> - *"table"*: `refGene`
204-
> - *"region"*: `genome`
205-
> - *"output format"*: `BED - browser extensible data`
205+
> - *"Clade"*: `Mammal`
206+
> - *"Genome"*: `Mouse`
207+
> - *"Assembly"*: `July 2007 (NCBI37/mm9)`
208+
> - *"Group"*: `Genes and Gene Predictions`
209+
> - *"Track"*: `RefSeq Genes`
210+
> - *"Table"*: `refGene`
211+
> - *"Region"*: `Genome`
212+
> - *"Output format"*: `BED - browser extensible data`
206213
> - *"Send output to"*: `Galaxy` (only)
207214
>
208215
> 4. Click on the **get Output** button
@@ -486,10 +493,10 @@ Great, we are ready to plot things!
486493
> 4. Choose a title below **Title**, e.g. `Gene counts per chromosome`
487494
> 5. Switch to the **Settings** tab and change the axis labels
488495
> 6. Play around with the settings in the **Tracks** tab
489-
> 7. When you are happy, click the {% icon download-cloud %} to **Save** visualization in the top right of the *main panel*
496+
> 7. When you are happy, click the {% icon cloud-upload %} icon to **Save** visualization in the top right of the *main panel*
490497
>
491498
> This will store it to your saved visualisations. Later you can view,
492-
> download, or share it with others by clicking on **Visualization** -> **Saved Visualizations** on the left menu bar. In the main panel you can find your saved plot.
499+
> download, or share it with others by clicking again on **Visualization** on the left menu bar. In the opened menu bar click on the blue **Saved Visualizations** button on top. In the main panel you can find your saved plot.
493500
>
494501
{: .hands_on}
495502

@@ -663,7 +670,7 @@ It's time to reuse the workflow we created earlier.
663670
664671
> <hands-on-title>Run a workflow</hands-on-title>
665672
> 1. Open the workflow menu (left menu bar)
666-
> 2. Find the workflow you made in the previous section, and select the option **Run**
673+
> 2. Find the workflow you made in the previous section, and select the option **Run** {% icon workflow-run %}
667674
> 3. Choose as inputs our `mm9.RefSeq_genes` (`#genes`) BED file and the result of the **Cut** tool (`#peaks`)
668675
> 4. Click **Run workflow**
669676
>
@@ -677,23 +684,24 @@ But wouldn't it be more interesting to know the number of peaks in each unique g
677684
> <hands-on-title>Run a workflow with changed settings</hands-on-title>
678685
> 1. Open the workflow menu (left menu bar)
679686
> 2. Find the workflow you made in the previous section, and select the option **Run**
680-
> 3. Choose as inputs our `mm9.RefSeq_genes` (`#genes`) BED file and the result of the **Cut** tool (`#peaks`)
681-
> 4. Click on the title of the {% icon tool %} **Group** tool to expand the options.
682-
> 5. Change the following settings by clicking on the {% icon galaxy-pencil %} (pencil) icon on the left:
687+
> 3. Click on **Workflow run settings** {% icon galaxy-wf-options %} and then on **Expanded workflow form**
688+
> 4. Choose as inputs our `mm9.RefSeq_genes` (`#genes`) BED file and the result of the **Cut** tool (`#peaks`)
689+
> 5. Click on the title of the {% icon tool %} **Group** tool to expand the options
690+
> 6. Change the following settings by clicking on the {% icon galaxy-pencil %} (pencil) icon on the left:
683691
> - *"Group by column"*: `7`
684692
> - In *"Operation"*:
685693
> - *"On column"*: `7`
686-
> 6. Click **Run workflow**
694+
> 7. Click **Run workflow**
687695
{: .hands_on}
688696
689697
Congratulations! You should have a file with all the unique gene names and a count on how many peaks they contained.
690698
691699
> <question-title></question-title>
692700
>
693-
> The list of unique genes is not sorted. Try to sort it on your own!
701+
> The list of unique genes is not sorted or you workflow included a sorting step but for the gene names. Try to sort it on your own!
694702
>
695703
> > <solution-title></solution-title>
696-
> > You can use the tool "Sort data in ascending or descending order" on column 2 and "fast numeric sort".
704+
> > You can use the tool "Sort data in ascending or descending order" or rerun to sort tool of your workflow. Sort on column 2 and "fast numeric sort".
697705
> {: .solution }
698706
{: .question}
699707
@@ -702,16 +710,16 @@ Congratulations! You should have a file with all the unique gene names and a cou
702710
703711
One of the most important features of Galaxy comes at the end of an analysis. When you have published striking findings, it is important that other researchers are able to reproduce your in-silico experiment. Galaxy enables users to easily share their workflows and histories with others.
704712
705-
To share a history, click on the {% icon galaxy-history-options %} history options and select `Share or Publish`. On this page you can do 3 things:
713+
To share a history, click on the {% icon galaxy-history-options %} history options and select `Share & Manage Access`. On this tab (**Share or Publish**) you can **Make History accessible** or **Share History with Individual Users**:
706714
707715
708-
1. **Make accessible via Link**
716+
1. **Make History accessible**
709717
710718
This generates a link that you can give out to others. Anybody with this link will be able to view your history.
711719
712-
2. **Make History publicly available in Published Histories**
720+
2. **Make History publicly available**
713721
714-
This will not only create a link, but will also publish your history. This means your history will be listed under `Data → Histories → Published Histories` in the top menu.
722+
This will not only create a link, but will also publish your history. This means your history will be listed under `Histories → Published Histories` in the left menu and other users can access the history there.
715723
716724
3. **Share with Individual Users**
717725
@@ -725,7 +733,7 @@ To share a history, click on the {% icon galaxy-history-options %} history opti
725733
> 2. See if you can do the same with your workflow!
726734
> 3. Find the history and/or workflow shared by your neighbour
727735
>
728-
> Histories shared with specific users can be accessed by those users under `Data → Histories → Histories shared with me`.
736+
> Histories shared with specific users can be accessed by those users under `Histories → Shared with Me`.
729737
>
730738
{: .hands_on}
731739

0 commit comments

Comments
 (0)