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

Multiples genomes #113

Open
SergioBuenestadoSerrano opened this issue May 31, 2023 · 1 comment
Open

Multiples genomes #113

SergioBuenestadoSerrano opened this issue May 31, 2023 · 1 comment

Comments

@SergioBuenestadoSerrano
Copy link

SergioBuenestadoSerrano commented May 31, 2023

Hello!

I'm experiencing some issues with RAMPART and I'm wondering if there is a solution available. I would like to know if anyone has been able to resolve similar problems.

In our laboratory, we have been using RAMPART for some time and it has always worked well. Now, we are trying to perform amplicon sequencing of specific regions of interest, but we are unsure how to prepare the files for proper analysis and visualization.

Here are a series of images and the desired outcomes that we would like to achieve. We would like to confirm if it is possible or if we need to perform separate analyses.

The first step we took was to create the genome.json and references file containing the sequences of our target amplicons. We represented it as a continuous fasta-like sequence with Ns separating both sequences.

  • Genome.json:
    {
    "label": "Amplicon Set",
    "length": XXX,
    "reference": {
    "label": "Amplicons",
    "accession": "Amplicons",
    "sequence": "sequence1NNNNNNNNNNNNNNNNNNNNsequence2"
    }
    }

  • References.fasta:

Amplicons
sequence1NNNNNNNNNNNNNNNNNNNNsequence2

Looking at the output, we can see that it nicely distinguishes the two amplicons as separate peaks, separated by the manually introduced Ns. However, in the "References matches" section, it shows the total percentage with only the single fasta sequence we inputted.

Screenshot from 2023-05-31 14-28-00

I decided to modify the genome.json and references.fasta files as follows:

  • Genome.json:

  • {
    "label": "Amplicons Abscessus/Chimaera",
    "length": (length_sequence1 + length_sequence2),
    "Amplicon1": {
    "label": "sequence1",
    "accession": "sequence1",
    "sequence": "CAAGTAGCCGTCAACGACATCGGCTCGGCCGAGGATTTTCTCGCCGCTATCGACAAGACGATCAAGTACTTCAACGATGGCGACATCGTCGAAGGGACCATCGTCAAGGTTGACCGCGACGAAGTTCTTCTTGACATCGGTTACAAGACCGAAGGTGTCATCCCGTCCCGCGAGCTCTCGATCAAGCACGA"
    },
    "Amplicon2": {
    "label": "sequence2",
    "accession": "sequence2",
    "sequence": "CAAGTAGCCGTCAACGACATTGGCTCCAGCGAGGACTTTCTCGCCGCAATAGACAAAACGATCAAGTACTTCAACGATGGCGACATCGTCGAGGGCACGATCGTCAAAGTGGACCGGGACGAGGTGCTCCTCGACATCGGCTACAAGACCGAGGGGGTCATCCCCGCCCGCGAGCTCTCGATCAAGCACGA"
    }
    }

  • References.fasta:

Sequence1
sequence1
Sequence2
sequence2

Screenshot from 2023-05-31 14-23-57

However, the result was not as expected. Now I only see a continuous peak without distinguishing the different amplicons. Although the "references matches" section provided exactly what I needed, merging the files by using the genome.json from the first step and the references.fasta from the second step did not change the result.

Even with the inclusion of Ns in the genome.json file to manually separate the two amplicons, it still didn't work as expected. The manual separation attempt did not produce the desired result.

Could anyone let me know if they have achieved the desired outcome or have any ideas on how to accomplish it?

Thank you very much in advance, any help or idea is welcome.

@danieljbridges
Copy link

Was just about to try to do the same thing as you @SergioBuenestadoSerrano so can't give you a solution, but am very keen to find one....

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

No branches or pull requests

2 participants