-
Notifications
You must be signed in to change notification settings - Fork 2
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 running PARAFAC decomposition #7
Comments
Hi Miguel, Thank you for a detailed report! The decomposition itself seems to have worked and what failed were the downstream time mode evaluation. To see if the decomposition itself ran, could you please check the logs for each partition (i.e. batch) of decompositions:
You can also search for model files (with the *.pt extension), by running the command below, which will also list how large these files are:
I think you can actually try CANDIA with real data but of course I should provide better test data. Actions on my part:
Best regards, |
Hello Filip, Thanks for the observations. I will take a look into this and would let you know. I have an additional question regarding the potential outputs from CANDIA, to see if I am understanding its usability correctly and test accordingly. After PARAFAC decomposition, should I expect to have a set of mzML files that can be then used for searching with traditional search engines? If so, where would I find those 'decomposed' spectral files? Let me know if you would prefer me to open a new issue with this question. Best wishes, |
Hi again Miguel, The output of the pipeline is a single mzXML file which contains decomposed spectra. This can be used for searching with existing search engines. If you need a file in mzML format, packages like OpenMS can be used to convert. The sequence leading to this output is as follows, keeping the numbering in the README:
The fact that the script for step 8 both exports the mzXML and performs the search reflects the workflow of the paper, but I think it should be split, for flexibility of use. This is pretty simple to do, and I opened an issue for it #10 . For now, if you wish to use different engines, a workaround is to simply run the script to produce the output but expect it to fail when it tries running Crux. Best, |
Hello Filip, Many thanks for your input! We have tested candia with our own data and it runs nicely until step 9. I am having an error when executing step 10.
I modified the sample yaml file to include I am attaching the yaml configuration that I am using. Many thanks in advance for taking a look! Best, |
Hi Miguel, My pleasure, happy that it works for you so far! For step 10, it looks like a bug. The I will fix this asap, thought this week is a bit packed. I opened issue #12 for this. Until then, a workaround is to add Best, |
Hello Filip,
We manage to install the CANDIA singularity container on a DENBI Ubuntu server with 2 cuda-able GPUs.
We are still not able to make the test command
./candia test/test_experiment/config/candia.yaml
run through completely.Actually, it throws an error at the stage of PARAFAC decomposition. The previous steps of the processing seem to run through. The error is persistent even if I execute the commands separately for each stage.
Something like:
I am attaching here the log of the execution including the results of the previous steps and the complete error.
error_report_CANDIA.txt
Do you think there's something we might be missing in the installation? What would you suggest to trouble-shoot this?
Many thanks in advance for taking a look into this.
Best wishes,
Miguel
The text was updated successfully, but these errors were encountered: