Added the new tool query_impc

[AndreaFurlani]

Sorry I made some mistakes with the old branch and I had to create a new one

FOR CONTRIBUTOR:

• - I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
• - License permits unrestricted use (educational + commercial)
• - This PR adds a new tool or tool collection
• - This PR updates an existing tool or tool collection
• - This PR does something else (explain below)

[bgruening]

@AndreaFurlani the tests are failing here. Do you need help figuring that out? Also please use macros to reduce the repeating elements in your wrapper.

[AndreaFurlani]

@AndreaFurlani the tests are failing here. Do you need help figuring that out? Also please use macros to reduce the repeating elements in your wrapper.

Hi @bgruening, yes thanks it would be helpful

[bgruening]

Cool, much better. Now the test needs to be fixed :)

[AndreaFurlani]

Hi @bgruening , I'm continuously get the following error during the tests:

Error_message.txt

[bgruening]

@AndreaFurlani your local Galaxy instance is too old. As we have added a more recent profile version here.

However, on github the Galaxy version is newer that we use for testing so the error message here in the CI is different.

You can download the tool error reports from this summary page: https://github.com/galaxyproject/tools-iuc/actions/runs/6338840242?pr=5503

Click on All tool tests results:

If you do that you see three errors:

One "parameter 'g_out': an invalid option ('txt') was selected (valid options: sym,mgi)"

the other "Error: it was not possible to map the input."

And the last "Output output: Test output file (test_output.tab) is missing. If you are using planemo, try adding --update_test_data to generate it."

[AndreaFurlani]

Hi @bgruening , now the tests are running correctly.
I noticed that there is still a check that is failing but I cannot get any error/log for that one. Does it need an input from our side?
Thank you for your advice

[bgruening]

Wonderful, I have created INFRAFRONTIERDIB#1 and added a few more comments there.

[bgruening]

2 errors are:

test 3 and 5.

and test 4 is:

[AndreaFurlani]

2 errors are:

test 3 and 5.

and test 4 is:

I saw the reports, but still I don't get it why the tests are failing. Inputs are correct since by removing the conditionals they all succeed

[bgruening]

Last comments. You can accept them in the GitHub interface.

I can not edit your files directly, you need to give us permission when you create the PR. If you do that I can do the small changes next time.

[bgruening]

Thanks a lot @AndreaFurlani. Great contribution!

If this gets merged it will be automatically deployed to the Galaxy ToolShed. If you would like to see this tool on the European Galaxy Server you can follow step 3 here: https://usegalaxy-eu.github.io/posts/2020/08/22/three-steps-to-galaxify-your-tool/

Thanks again!

[AndreaFurlani]

Thanks a lot @AndreaFurlani. Great contribution!

If this gets merged it will be automatically deployed to the Galaxy ToolShed. If you would like to see this tool on the European Galaxy Server you can follow step 3 here: https://usegalaxy-eu.github.io/posts/2020/08/22/three-steps-to-galaxify-your-tool/

Thanks again!

Thank you again @bgruening for all the help. We are going to follow step 3 then to get our tool on the European Galaxy Server.

[AndreaFurlani]

Thanks a lot @AndreaFurlani. Great contribution!

If this gets merged it will be automatically deployed to the Galaxy ToolShed. If you would like to see this tool on the European Galaxy Server you can follow step 3 here: https://usegalaxy-eu.github.io/posts/2020/08/22/three-steps-to-galaxify-your-tool/

Thanks again!

Hi @bgruening , regarding step 3 do I need to create a new branch or can I push on this one directly after creating the yaml file? Also it is not clear how should I call it. Thank you for the help

[bgruening]

Hi @AndreaFurlani. You need to create a fork of the repo, change the tools_iuc.yml file and create a PR.