Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:06
    joshsadam opened #1284
  • May 22 16:37
    deepsidhu85 synchronize #1279
  • May 22 16:29
    deepsidhu85 synchronize #1279
  • May 22 16:20
    deepsidhu85 synchronize #1279
  • May 22 03:33
    ericenns edited #1280
  • May 22 03:29
    ericenns synchronize #1280
  • May 21 20:38
    ericenns synchronize #1280
  • May 21 16:17
    ericenns edited #1280
  • May 21 16:16
    ericenns assigned #181
  • May 21 16:16
    ericenns assigned #252
  • May 21 04:59
    ericenns synchronize #1280
  • May 21 04:38
    ericenns synchronize #1280
  • May 21 02:06
    ericenns synchronize #1280
  • May 20 23:04
    ericenns synchronize #1280
  • May 20 22:22
    ericenns synchronize #1280
  • May 20 21:54
    apetkau synchronize #1282
  • May 20 21:35
    apetkau synchronize #1282
  • May 20 21:24
    apetkau synchronize #1282
  • May 20 21:14
    apetkau closed #1276
  • May 20 21:13
    apetkau synchronize #1282
Aaron Petkau
@apetkau
However, realistically, depending on how much time you want to spend checking and validating your SQL (and learning the IRIDA database structure) it might just be easier to re-upload the sequence data anyways
Karin Lagesen
@karinlag
I was wondering about that
because I did have the impressin that reuploading it would just mean that we would have 2 copies of the data in the backend
Aaron Petkau
@apetkau
Yes, you would have 2 copies. But it's also less work than messing around with the internal tables/SQL in the database. Tradeoffs with each approach (we've re-uploaded a lot of data in our database too and have duplicate sequence files).
Aaron Petkau
@apetkau

The actual code that gets called when you remove sequence data from a sample is:

https://github.com/phac-nml/irida/blob/development/src/main/java/ca/corefacility/bioinformatics/irida/ria/web/samples/SamplesController.java#L426-L445

Specifically, here you can see that what it does is removes the link between a sample and a sequencing object (that is a row from the sample_sequencingobject table). So restoring the entry in this table restores the sample/sequence data link.

Aaron Petkau
@apetkau
image.png
The different REVTYPE values in case you wanted to see what they all represent (from https://docs.jboss.org/hibernate/orm/current/userguide/html_single/Hibernate_User_Guide.html#envers)
Jeevan Karloss
@ajkarloss
@apetkau Thanks a lot.
Jeevan Karloss
@ajkarloss

@apetkau I am getting this Error

AnalysisSubmission [id=11, name=SISTR__1-11-2022_Test_1, submitter=admin, workflowId=b21ea62c-7916-4ca6-96ba-90c20177b70f, analysisState=PREPARING, analysisCleanedState=NOT_CLEANED] changing to state ERROR
ca.corefacility.bioinformatics.irida.exceptions.galaxy.WorkflowUploadException: Could not upload workflow from /workflows/1.1.1/irida_workflow_structure.ga
at ca.corefacility.bioinformatics.irida.pipeline.upload.galaxy.GalaxyWorkflowService.uploadGalaxyWorkflow(GalaxyWorkflowService.java:64) ~[classes/:?]

No New history is being created

Is it something to do with file sharing or?

Aaron Petkau
@apetkau
Can you try uploading the SISTR workflow to Galaxy to see if all the tools are installed?
Jeevan Karloss
@ajkarloss
Yes, that works
Aaron Petkau
@apetkau
Are all other pipelines working, just not SISTR?
Is there anything in the Galaxy log files at around the same time as trying to run SISTR?
Eric Enns
@ericenns
@ajkarloss Is the IRIDA data filesystem accessible on the galaxy server? See point 2 here https://phac-nml.github.io/irida-documentation/administrator/galaxy/existing-galaxy/
Jeevan Karloss
@ajkarloss
@apetkau All the workflows are working fine in galaxy :)
@ericenns I am able to access the irida data from galaxy
Aaron Petkau
@apetkau
@ajkarloss all the workflows as in you are able to run SISTR now? Or is SISTR not working still?
Jeevan Karloss
@ajkarloss
SISTR: Is it possible to update the cgMLST330 to ~3000 loci?
Aaron Petkau
@apetkau
No, SISTR was designed with 330 loci.
You could look into other Salmonella MLST schemes though (e.g., from enterobase https://enterobase.warwick.ac.uk/)
Jeevan Karloss
@ajkarloss
@apetkau Thanks
Zipho Mashologu
@zipho

Hi, I am having this issue whenever trying to run an analysis

ca.corefacility.bioinformatics.irida.exceptions.galaxy.WorkflowUploadException: Could not upload workflow from /workflows/0.1.5/irida_workflow_structure.ga

Galaxy logs throw the uwsgi issue, could they be related.
[uwsgi-http key: localhost:9090 client_addr: 127.0.0.1 client_port: 50636] hr_instance_read(): Connection reset by peer [plugins/http/http.c line 647]

any pointers will be greatly appreciated.
Jeevan Karloss
@ajkarloss

@zipho, seems like irida/tomcat does not have permission to upload the file to galaxy.

Can galaxy user from galaxy VM able to login to irida VM and vice-versa?

Aaron Petkau
@apetkau
@zipho is this only for a particular analysis pipeline, or for all analysis pipelines?
I'm not sure if the uwsgi issue is related. I guess peer in this case could be IRIDA (if that message is from Galaxy) so could be produced during the error in uploading the workflow. But I'm not sure.
@ajkarloss do you mean does IRIDA and Galaxy share user accounts? No, they do not. A user account in Galaxy is different from a user account in IRIDA.
Or do you mean the user running the Galaxy and IRIDA software? This depends on how you have set things up, but in general no they are likely separate accounts.
Jeevan Karloss
@ajkarloss
@apetkau No, I dont mean " IRIDA and Galaxy share user accounts".
Jeevan Karloss
@ajkarloss

SNVPhy_Pipeline throws this exception when we use many samples.

Exception: Header does not correspond to PHYLIP header.

Any tips?

Aaron Petkau
@apetkau

It's likely that some genomes are either very low coverage or too different from the rest and all SNV/SNP data is removed from the phylip alignment file. You can check the mapping quality file (https://snvphyl.readthedocs.io/en/latest/user/output/#mapping-quality) for information on which genomes have low coverage. You can check the core positions file to find the percent of the reference genome considered for data analysis.

If you find any genomes with too low of coverage or too distantly related you can remove them from analysis and re-run SNVPhyl

You may also want to disable SNV density filtering too if it is enabled (https://phac-nml.github.io/irida-documentation/user/tutorials/snvphyl/#required-parameters-density-filtering). This can cause issues if some genomes are very distant from others (leading to many SNVs/SNPs between them)
Jeevan Karloss
@ajkarloss
@apetkau Thanks. I will test and try that :)
Eric Enns
@ericenns
January release of IRIDA is now available. https://github.com/phac-nml/irida/releases/tag/22.01
Jeevan Karloss
@ajkarloss
@ericenns Thanks s:)
Screenshot 2022-01-30 at 21.38.55.png
I am getting those error while loading the IRIDA plugins and I dont see the added JAR files in on the web. Any tips?
Aaron Petkau
@apetkau
@ajkarloss I can see multiple IRIDA war files listed in the log irida-21.09.2.war and irida.war. Is it possible you are deploying multiple instances of IRIDA and one of them is an old version?
You likely want to figure out which one you want to deploy and rename it to irida.war (so IRIDA is available at http://address/irida).
Jeevan Karloss
@ajkarloss
Thanks @apetkau
Screenshot 2022-02-03 at 14.31.51.png
I have installed irida-galaxy-importer. When I click the irida uploader in galaxy, it takes to IRIDA and .... what is next? I dont see any option to click or something to share the data :)
2 replies
Eric Enns
@ericenns
We are pulling the 22.01 IRIDA release, there are bugs present in the REST API that we did not encounter till we deployed the release internally.
Eric Enns
@ericenns

We are pulling the 22.01 IRIDA release, there are bugs present in the REST API that we did not encounter till we deployed the release internally.

The issue we had was do to us modifying headers in apache httpd, but 22.01 broke the format of the REST API by changing the response format of date fields. We are going to revert this and release a hotfix shortly.

Eric Enns
@ericenns

We are pulling the 22.01 IRIDA release, there are bugs present in the REST API that we did not encounter till we deployed the release internally.

The issue we had was do to us modifying headers in apache httpd, but 22.01 broke the format of the REST API by changing the response format of date fields. We are going to revert this and release a hotfix shortly.

Hotfix has been tested and corrects the REST API back to previous behaviour. It can be found on our github and we have a discussion here https://github.com/phac-nml/irida/discussions/1189.

pvanheus
@pvanheus
Woohoo! HTML support! I'm looking forward to testing this... is this still supporting a single HTML file within the zipped output from Galaxy or does it support HTML + assets?
Aaron Petkau
@apetkau
Thanks @pvanheus
It's only a single HTML file
HTML + assets will have to come later