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
error 'cannot get position' when running bam2gam.sh #72
Comments
chr7 of length in hg19 is 159138663, so I suspect that chr7 in
Also, did you see any error messages when you run |
Thank you again for your continued support. Here's the output:
It is indeed truncated.
|
When MoMI-G tools are executed in Singularity, Singularity seems to discard the original stderr. I assume that the error messages were lost due to this behavior. I modified the script to output messages to stdout, so is it possible to run singularity again? Also, you can validate the gfa format via |
I've re-run vg from docker, but it doesn't seem to have a more useful error messages other than "potentially truncated"
I wasn't able to compile gfalint, so I can't validate the gfa format. |
Is it possible to check if $ grep chr7 ~/hg19/hg19.fa.fai
chr7 159138663 1258330213 50 51
chr7_gl000195_random 182896 3195389782 50 51 The output |
I have the same thing:
|
Are other chromosomes truncated? |
This is what I got from the above command:
I'm confused. Isn't this checking whether chromosomes are truncated in my momig_input.xg? But, the chr7 is no longer truncated? |
Strange, but anyway, it seems no longer truncated. |
It is strange. Don't know what happened... I was able to run bam2gam.sh to completion. Thank you! But the output files do not have any names. These are the output files:
and these are the commands I ran:
|
The fourth argument of singularity exec --pwd ~/opt/MoMI-G/scripts docker://momigteam/momig-tools:autobuild bash -x bam2gam.sh ~/Data/A673_pacbio/HiFi/bam/A673.HiFi.hg19.sorted.md.bam ~/Data/A673_pacbio/HiFi/vcf/momig_input.xg /vg/bin/vg prefix |
Great! Thank you! |
@6br, I was able to generate .gam and gam.index files/folder. But, the SequenceTubeMap is not displayed.
and this is the error from the backend-server:
fyi, I just realized that running example CHM1 data on my own backend-server also doesn't display SequenceTubeMap. Thank you again for your help. |
For the problem that running example CHM1 data on my own backend-server also doesn't display SequenceTubeMap, this might be related with #70 . I will check the behavior and update the codes if needed. |
For CHM1 data, my singularity environment works. Note that the CHM1 example contains only the region on chr21. e.g. |
I'm not sure how to navigate to the exact location that you referenced above for the CHM1 example data. Tried copy pasting that address in firefox but it doesn't look like it's doing anything. edit: I tried |
Looks like I was using vg version 1.25:
So, I tried your command to get vg 1.25 for backend-server, but I think it's still getting version 1.6 and I still have the same internal server error:
I'm going to try to re-generate the files using |
Tried to run vg 1.6 but got an error:
|
For CHM1 demo, For For Internal Server Error, the old version of Also, is it possible to specify
|
For CHM1 demo, Thanks for fixing the bug I'll try to use the |
I tried to run the following to display CHM1 demo running my own backend server using
|
For CHM1 demo, that's strange... I run the same command on my environment. I recommend to use |
I still cannot get both CHM1 demo and my own data to display SequenceTube. I don't know if this helps, but I noticed in your CHM1 demo log, you have |
There are possible causes of the behavior.
|
Did you see any return message when you access to Also, to help to identify the cause of this behavior, now I updated the debug messages on
|
I tried run singularity with
This time, I was able to navigate to It's |
I think I got further by binding
|
Sorry for the different scenarios back and forth with CHM1 demo and my own data. I hope it's not too confusing.
I'm very happy to make such a progress. Unfortunately, for some entries, the SequenceTube still is not displayed. It's no easy to see from the log, since the actual SV that I clicked was not visible in the log. For example, these are the SVs that I clicked in the order shown below:
These are the messages shown on the backend server as I clicked on the SVs above:
For those that doesn't display a graph, the previously displayed graph was just on the web browser nothing else is changed. |
For CHM1 demo, I am wondering why vg binary cannot find xg file. Now I changed the path |
Actually, when the interval to visualize is longer than 1 Mbp, retrieving chunks by vg becomes slow. Thus, MoMI-G backend restricts the maximum interval to visualize. If users wish to see the large variants, then push "left-align" or "right-align" button on the interval card deck. The variants can be visualized by retrieving subgraphs from the either of breakends. The maximum length of the specified genomic range is limited by the singularity exec --bind ~/Data/A673_pacbio/HiFi/vcf:/vg/static --bind /tmp:/vg/tmp --pwd /vg docker://momigteam/momig-backend:prod /vg/graph-genome-browser-backend --config=/vg/static/config.yaml --interval=2000000 --http=0.0.0.0:8081", "--api=/api/v2/ Still, I wouldn't recommend to set much longer interval because it causes the performance problem. |
Thanks for the screen shot. That is a great option that I didn't realize before. I tried the CHM1 demo again but still have the same "unable to load xg index file". I'm not sure why. I thought the absolute path will fix it.
Since I was able to display my own data in MoMI-G, I'm not going to worry about the CHM1 data anymore. Unless you want me to still trouble shoot it. |
I am glad to hear that you can visualize on your data in MoMI-G. Thank you for using MoMI-G and helping us debug MoMI-G. When you have any question, feel free to ask. |
@6br |
Hi,
I'm trying to run bam2gam for my own dataset with the following command:
singularity exec --pwd /home/xxt050/opt/MoMI-G/scripts docker://momigteam/momig-tools:autobuild bash -x bam2gam.sh /home/xxt050/Data/A673_pacbio/HiFi/bam/A673.HiFi.hg19.sorted.md.bam /home/xxt050/Data/A673_pacbio/HiFi/vcf/momig_input.xg /vg/bin/vg
and encountered this error:
The
momig_input.xg
was generated using:singularity run docker://momigteam/momig-tools:autobuild ~/Data/A673_pacbio/HiFi/vcf/A673.HiFi.hg19.sniffles.TRA.vcf momig_input ~/opt/vg ~/hg19/hg19.fa
Can you please help me figure out how to fix this?
The text was updated successfully, but these errors were encountered: