CWL viewer does not seem to work (at least for me) properly. Although the homepage is intact, the workflows can not be visualized. I am not sure if this is the right channel to raise this issue about CWL viewer (https://view.commonwl.org/).
1 Like
Hey @HrishiDhondge ; thanks for the feedback and I’m sorry that the CWL viewer isn’t working well lately.
In the mean time, you can get the same or similar visualization from one of the following ways
-
Register your CWL workflow on the WorkflowHub
Example: (Hybrid) Metagenomics workflow -
Visualize locally using
cwltool: https://carpentries-incubator.github.io/cwl-novice-tutorial/03-dependency_graphs/index.html#from-cwl-script-to-graph -
Visualize using the Benten CWL language plugin for VSCode: https://github.com/rabix/benten#features
1 Like
cwlviewer looks to be working right now for me. Do you have a link to your code that you want to visualize so we can see what the possible issue might be? Thank you.
It is working now for me as well. It was not working when I raised this issue. Thank you!
2 Likes
Great. We are having some memory issues with the tool - and it stops working momentarily. Hopefully the next bug fix by Bruno will solve the issue.
1 Like
I tried to register my Workflow on workflowhub, I applied to create the team and received no answer from the administrators to validate the team. Do I need to contact them via mail or something?
If I have my gitlab repository on an institution’s GitLab instance, can I visualize it normally using CWLviewer?
Whenever I paste the link of the workflow, it can not parse.
Hello - you should be able to use cwltoor options if cwlviewer isn’t working –
–print-rdf Print corresponding RDF graph for workflow and exit
–print-dot Print workflow visualization in graphviz format and
exit
to view w/o running. It isn’t exactly the same as cwl-viewer but can get you a recent visualization.
If you send us the link, maybe Bruno could help?
@kinow do you thinking you could see what the issues is with cwl-viewer?
1 Like
This is the workflow.
1 Like
It seems to be a bug - I put in an issue for you here:
1 Like
Self-hosted GitLab repositories (those not on gitlab.com) should instead past in the Git URL (https://gitlab.inria.fr/capsid.public_codes/CroMaSt.git in your case) and then enter the branch name and path to the workflow in the form that appears:
For example, here is your workflow: https://w3id.org/cwl/view/git/e5ae19d24ba0a5553d8ca57ec8b2c323e04427ea/CroMaSt.cwl
We are working on changes to the view.commonwl.org website to make this more clear, and maybe in the future this workaround won’t be needed
2 Likes