Menu ▾ ▴

#269 Can't load genomes

IGB_6_7
open
nobody
None
1
2015-09-30
2015-09-29
Adam Blattler
No

Hello,

I'm running IGB 8.4.4 and have recently run into the issue of not being able to load the default IGB quickload genome for hg19 (although it seems other genomes are effected as well). I have already tried uninstalling and reinstalling, but run into the same problem. This issue occurs about 90% of the time upon opening IGB. I have attached screenshots of some error messages.

Adam

3 Attachments
Screenshot 2015-09-29 14.25.37.png
Screenshot 2015-09-29 14.27.50.png
Screenshot 2015-09-29 14.31.26.png

Discussion

  • Mason Meyer

    Mason Meyer - 2015-09-29

    Hello Adam,

    Thank you for taking the time to let us know this is happening. We apologize for any inconvenience this may have caused you.

    Our team will take a deeper look into this issue to see why it is happening and get back to you very shortly with some information.

    In the meantime, you may want to try refreshing your data sources to see if that fixes the problem.

    To do this, select Preferences in the File menu at the top of IGB to open up IGB Preferences, then select the Data Sources tab. In the Data Sources tab you can click the small blue arrows to the left of each data source to refresh that source. Do that for each data source listed and then try to load a genome.

    Hopefully this will fix the issue you are having. I will get back to you shortly after discussing this issue with the rest of the team.

    Thanks again for your feedback.

     

  • Mason Meyer

    Mason Meyer - 2015-09-30

    Hello again Adam,

    I just wanted to follow up with you to check if you had a chance to try refreshing your data sources and see if this resolved your problem.

    If it did not, would you mind copying the logs from the IGB console? You can do this by going to the Help menu at the top of IGB and clicking Show Console. This console tracks what IGB is doing in the background. Try to load a genome again with the console open and if you run into the issue you are having again, just copy all of the text in the console and post it in a comment below.

    This console can give our team the necessary information to take a deeper look into your problem. Hopefully, you are no longer experiencing the issue you had, but if you are, please let us know if you have time so that we can figure out a way to resolve the problem for you.

    Once again, thank you very much for providing us with your feedback.

     
MongoDB Logo MongoDB