Details
-
Type:
New Feature
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.11.0
-
Fix Version/s: None
-
Component/s: slivka, trees, web service request
-
Labels:None
-
Urgency:Month of sundays
Description
An attendee at a Jalview futures talk asked about linking Jalview to CIPRES' RESTful API.
From the website (https://www.phylo.org/): The CIPRES Science Gateway V. 3.3 is a public resource for inference of large phylogenetic trees. It is designed to provide all researchers with access to NSF XSEDE's large computational resources through a simple browser interface. You can also access these same capabilities programatically with the CIPRES REST API.
The REST API requires (what appears to be free) user registration, although the attendee mentioned institutional accounts too.
CIPRES REST API announcement: http://www.phylo.org/index.php/news/detail/announcing-cipres-restful-services-a-new-way-to-use-cipres
Developer docs: https://www.phylo.org/restusers/documentation
I haven't explored any of the capabilities of the API so don't know what "functionality" means here.
Thought: Incorporating it into Jalview through Slivka (so little/no Jalview development required, and institutional access could be arranged through a local Slivka server[??]).
From the website (https://www.phylo.org/): The CIPRES Science Gateway V. 3.3 is a public resource for inference of large phylogenetic trees. It is designed to provide all researchers with access to NSF XSEDE's large computational resources through a simple browser interface. You can also access these same capabilities programatically with the CIPRES REST API.
The REST API requires (what appears to be free) user registration, although the attendee mentioned institutional accounts too.
CIPRES REST API announcement: http://www.phylo.org/index.php/news/detail/announcing-cipres-restful-services-a-new-way-to-use-cipres
Developer docs: https://www.phylo.org/restusers/documentation
I haven't explored any of the capabilities of the API so don't know what "functionality" means here.
Thought: Incorporating it into Jalview through Slivka (so little/no Jalview development required, and institutional access could be arranged through a local Slivka server[??]).