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

[BUG]: <title>FCS-adaptor results in an error in the log. #105

Open
Boom-WJ opened this issue Jan 6, 2025 · 1 comment
Open

[BUG]: <title>FCS-adaptor results in an error in the log. #105

Boom-WJ opened this issue Jan 6, 2025 · 1 comment

Comments

@Boom-WJ
Copy link

Boom-WJ commented Jan 6, 2025

Hello,

Thank you very much for your work on what seems to be a very exciting tool.

I tried to run FCS-adaptor and there is a difference between what is shown in the work log and what is partially shown in the operational example.

I tried to run FCS-adaptor and there is a difference between what is shown in the work log and what is partially shown in the operational example, which I will show in the log. I would like to know if this difference is correct.

Also the run result report shows that there is no adapter, but according to the Unevec database the comparison shows that there is an adapter, is the reason for this difference related to the previous question?

I would be most grateful if you could offer any insight?

Thanks in advance!

log:
[workflow ] completed success
Output will be placed in: /output-volume
Executing the workflow
Error response from daemon: No such container: run_av_screen_x
Error response from daemon: No such container: run_av_screen_x

@etvedte
Copy link
Contributor

etvedte commented Jan 6, 2025

The No such container: run_av_screen_x is a known issue for some users (see #103). It shouldn't be affecting output.

Also the run result report shows that there is no adapter, but according to the Unevec database the comparison shows that there is an adapter

Is this on your own data? what sequences are you expecting to find that are missing from FCS-adaptor reports?

Can you run the example from the wiki and see if you get the expected result?

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