VRE #7450

request for a VRE for IOTC working party (octobre / november 2017) : IOTC SS3 VRE

Added by Julien Barde over 1 year ago. Updated 10 months ago.

Status:ReleasedStart date:Sep 15, 2017
Priority:UrgentDue date:
Assignee:Massimiliano Assante% Done:

100%

Sprint:WP08
VRE_Policy:Restricted Invite_Policy:VRE_Manager
Milestones:
Duration:

Description

We will start working with IOTC and FAO on SS3 and stock assessment of billfish and tropical tuna.
As a pre-requisite, we need to run some tests to compile SS3 latest version on the infrastructure. If it works, we will need a new VRE for IOTC members to demonstrate how SS3 stock assesment codes can be reproduced and tuned with new parameters.
If ok, we would like a new VRE which would be a replication of ICCAT_BFT-E with additional services (when operationnal):
- SS3 latest version (as done for VPA)
- Sharelatex
- ShinyProxy
- dedicated Thredds catalog,
- CSW server / GN / CKAN metadata catalog displaying only datasets and processes in the VRE.

VRE_description_SS3.doc (32.5 KB) Julien Barde, Sep 15, 2017 07:24 AM

VRE_description_SS3.pdf (383 KB) Julien Barde, Sep 15, 2017 07:24 AM

SS3.24AB.24ab (3.32 MB) Anne Elise Nieblas, Sep 27, 2017 04:42 AM

Capture d_écran de 2017-10-03 19-03-20.png (89.9 KB) Julien Barde, Oct 03, 2017 07:06 PM

image001.jpg (100 KB) Julien Barde, Oct 20, 2017 11:25 AM

1718
1754

Subtasks

D4Science Infrastructure - VM Creation #9779: GeoNetwork 3 dedicated instance for IOTC SS3Closed_InfraScience Systems Engineer

D4Science Infrastructure - VM Creation #9809: Ceate a new CKAN instance for IOTC: ckan-iotc.d4science.orgClosed_InfraScience Systems Engineer

Task #10124: Basic configuration for IOTC CatalogueClosedCostantino Perciante

Support #10295: Issue with the Workspace pathClosedAnne Elise Nieblas

Incident #10298: RStudio doesn't startClosedAnne Elise Nieblas


Related issues

Related to BlueBRIDGE - Incident #10005: Workspace shared folder copied into VRE shared folder has... Closed Oct 23, 2017

History

#1 Updated by Pasquale Pagano over 1 year ago

  • Invite_Policy set to VRE_Manager
  • VRE_Policy set to Restricted
  • Due date set to Oct 09, 2017
  • Tracker changed from Support to VRE

#2 Updated by Julien Barde about 1 year ago

  • % Done changed from 0 to 30
  • Subject changed from request for a VRE for IOTC working party (november 2017) : IOTC SS3 VRE to request for a VRE for IOTC working party (octobre / november 2017) : IOTC SS3 VRE

Would it be possible to have this VRE dedicated to SS3 for IOTC set up before the TCom (see specifications in the description above) ?
Anne Elise and me are going to be the administrators.

@anne.elise.nieblas@gmail.com has been working with RStudio (from RStudioLab) so far to compile SS3. Now she will present her work t the community in different meetings :

#3 Updated by Massimiliano Assante about 1 year ago

  • Status changed from New to Planned

#4 Updated by Pasquale Pagano about 1 year ago

  • Due date changed from Oct 09, 2017 to Sep 29, 2017

#5 Updated by Pasquale Pagano about 1 year ago

Hi @julien.barde@ird.fr, we can create the VRE with the following services:

  • RStudio
  • Sharelatex
  • ShinyProxy
  • dedicated Thredds catalog,
  • dedicated GeoNetwork
  • dedicated CKAN

Please confirm this list and provide us with a name of the VRE (short name without spaces) and a description of it.

#6 Updated by Julien Barde about 1 year ago

Hi @pasquale.pagano@isti.cnr.it ,
For the description, I will discuss with @anne.elise.nieblas@gmail.com first and get back to you.

Some comments regarding the different components of the VRE:

  • regarding Shinyproxy, we don't know how it works and if we need anything specific to the VRE. We just plan to host some shiny apps. Up to you to decide what is best.
  • dedicated Thredds catalog => a synchronization of a VRE WS folder with Thredds configuration file would be fine if we can easily configure our own catalog. In this case a dedicated Thredds instance wouldn't need a lot of machine resources.
  • dedicated GN => this should be an instance of GN in this case since e will generate metadata by following the same approach as the one used in the Tuna Atlas VRE (and we need to remove everything from time to time when we update the workflow)
  • dedicated CKAN => we just want CKAN to display only the resources managed by this VRE (as inputs or outputs). No need for a dedicated instance in this case
  • just like for ICCAT BFT-E, at some point we aim to deploy some algorithms as WPS with dataminer

#7 Updated by Julien Barde about 1 year ago

Please find in attached files the description of the VRE provided by @anne.elise.nieblas@gmail.com

#8 Updated by Roberto Cirillo about 1 year ago

Please, @julien.barde@ird.fr could you specify the GeoNetwork version you need?

#9 Updated by Julien Barde about 1 year ago

We would like to be in line with the version of Geonetwork used by Tuna Atlas VRE (geonetwork 3 as discussed in the ticket #9702) to be sure we can use the same scripts.

#10 Updated by Gianpaolo Coro about 1 year ago

Hi Julien, I cannot understand if

1 - your requirement is to have SS3 pre-installed on the RStudio, ShareLatex, and ShinyProxy machines;
2 - you will autonomously embed the SS3 in your project and manage it in your applications.

The NOAA SS3 download page (http://nft.nefsc.noaa.gov/Download.html) contains a number of modules that are compiled for Windows only. Some time ago, a FAO consultant asked NOAA for the source code, after my request, in order to try to compile SS3 on Linux. I have never received a follow-up, I don't know if you were able to get the Linux versions.

#11 Updated by Julien Barde about 1 year ago

Hi Gianpaolo,
indeed, my understanding is that we just need a pre-compiled version of SS3 for Linux (just like Fortran VPA) and this is fine like this.
@anne.elise.nieblas@gmail.com is already working with SS3 this way since April. She's using one RStudio server instance on the infrastructure and compiling SS3 with R Codes. She is in touch with NOAA team and has already dealt with various versions of SS3. She can tell more if some colleagues are blocked.
So I think we don't need anything particular for SS3.

#12 Updated by Gianpaolo Coro about 1 year ago

Hi Julien, thanks for the answer. So the process will be likely embedded in your processes. If it works on the other RStudio instances, it will work in the new VRE too.

#13 Updated by Julien Barde about 1 year ago

yes that's what we expect but, at some point, we might face issues according to the versions (this is what happened this year with the VPA for Linux which didn't work anymore since they used new parameters).

#14 Updated by Massimiliano Assante about 1 year ago

  • Status changed from Planned to In Progress

#15 Updated by Massimiliano Assante about 1 year ago

  • Status changed from In Progress to Available

The VRE is available (but not ready) at https://bluebridge.d4science.org/group/iotc_ss3

#16 Updated by Massimiliano Assante about 1 year ago

@julien.barde@ird.fr I just created a Public web page for this VRE with the content you provided at https://bluebridge.d4science.org/web/iotc_ss3/

Please validate it. If you want to edit the content you have editing permission on it, once logged in in the VRE top bar go to Admin > Site Administration > Content and edit the document with id 69881309 and name IOTC SS3 VRE

#17 Updated by Anne Elise Nieblas about 1 year ago

Hello, this is the Linux version that I use (v3.24), that I think we should have on the VRE. Please note, this is not the latest version, but the version that currently works for all the models we have available.

#18 Updated by Julien Barde about 1 year ago

@massimiliano.assante@isti.cnr.it is it possible for @anne.elise.nieblas@gmail.com to be an administrator / VRE manager since she will be the one in touch with IOTC and related working groups ?

#19 Updated by Massimiliano Assante about 1 year ago

Julien, as VRE Manager you can, in turn, assign the VRE Manager role to other users. In this portlet https://bluebridge.d4science.org/group/iotc_ss3/manage-user-and-requests you can assign her any role.

#20 Updated by Julien Barde about 1 year ago

ok sorry I never realized I was able to manage the roles with this portlet..I assigned the role "VRE-manager" to Anne-Elise.
Thanks

#21 Updated by Julien Barde about 1 year ago

@massimiliano.assante@isti.cnr.it : I understand that this VRE is not ready (#7450#note-15) and I don't know what is missing but I want to report two things:

  • Sharelatex is not working for now (see screenshot attached)
  • we woudl like to change the label "Shyny Proxy" in the upper menu to get "Interactive Dashboards" instead (same request as for ICCAT BFT-E VRE #9012#note-22)?

I also have a question: if we have sharelatex projects specific to a VRE, can we list them as children (sub menu) of the "Sharelatex" item (same principle as #9012#note-23) ? Some Sharelatex can be public (at least all VRE members) and some other will be private.

#22 Updated by Julien Barde about 1 year ago

@massimiliano.assante@isti.cnr.it , could you please let us know when the VRE will be ready ?

We noticed that Sharelatex is not connected, RStudio URL is not human readable for now and perhaps some other things which are not obvious for us and needs to be managed before using it.

We are presenting the work at IOTC since few days and we would like to know when it will be officially ready.

Thanks

#23 Updated by Julien Barde about 1 year ago

In addition to previous email,
there is one error for multiple users when connecting the VRE. Here is what @anne.elise.nieblas@gmail.com reported: "People were *actually * accessing the VRE, but could not open the ss324 folder - there was an error : an error occurred on the server when getting items from the grid - ....the VRE seems to be running very slowly" Perhaps due to a very low bandwith / Internet Connection

see attached image

#24 Updated by Massimiliano Assante about 1 year ago

@costantino.perciante@isti.cnr.it can you check the error on * accessing the VRE, but could not open the ss324 folder ?

#25 Updated by Julien Barde about 1 year ago

Just in case, if it helps, keep in mind the context: the Internet connection is very low there and multiple users registered and tried to access the VRE thereafter.

#26 Updated by Costantino Perciante about 1 year ago

I investigated a bit and the problem is related to the fact that the folder was originally shared among few users. For some reason, after the copy within the shared folder, the users allowed to access are still the old ones. Other vre shared folder's members cannot access.

I'm going to open a ticket for it

#27 Updated by Costantino Perciante about 1 year ago

  • Related to Incident #10005: Workspace shared folder copied into VRE shared folder has restricted access added

#28 Updated by Pasquale Pagano 12 months ago

Please fix manually the list of users that have to access the folder since the reported incident is not an incident for me (see my comments in that ticket) and it does not make sense to wait for its resolution.

#29 Updated by Costantino Perciante 12 months ago

Pasquale Pagano wrote:

Please fix manually the list of users that have to access the folder since the reported incident is not an incident for me (see my comments in that ticket) and it does not make sense to wait for its resolution.

We investigated a bit the problem, but there is no way to update the users that can access the folder under the VRE shared folder without drawbacks. Doing so, they will have a copy of the folder in their private workspace too.

The solution is going to be like this:

  • we will download the folder under the shared vre one;
  • we will reupload it in the vre shared folder again (as simple folder this time, no longer shared).

Now, and this is up to you @julien.barde@ird.fr and @anne.elise.nieblas@gmail.com , we could remove the bugged folder, but this would unshare it from your private workspaces. Is it ok for you?

Eventually you will have the folder shared once among all vre's members.

P.S.
The fixed workspace application won't allow you to copy a shared folder in a vre folder; it will automatically create a copy of the folder and share it among the vre members.

#30 Updated by Massimiliano Assante 12 months ago

@julien.barde@ird.fr the VRE services have been deployed and they are all in operation: THREDDS and dedicated GeoNetwork, 5 RSTUDIO nodes and a DataMiner cluster, ShareLatex, Shiny and the dedicated Data Catalogue.

We would need to know which algorithm you would like to make available on DataMIner, at the moment we added one as example taken from ICCAT. Can you check the VRE and provide us feedback?

#31 Updated by Julien Barde 12 months ago

@massimiliano.assante@isti.cnr.it, sorry for my late reply, we still can't see Geonetwork or Thredds in the VRE.

We are going to present these new services at the end of the month to IOTC.

As susggested by @emmanuel.blondel@fao.org it would be interesting to add two sub-items to the current "Data Catalogue" item in the upper menu (which I would like, by the way, to rename "Metadata Catalog"):

  • "CKAN catalog"
  • "Geonetwork catalog"

@anne.elise.nieblas@gmail.com is working on R codes to be deployed in dataminer and on a shiny application to be deployed (with the help of @nathan.vaughan1@gmail.com ?)

#33 Updated by Julien Barde 12 months ago

ok thanks.
Where can I get the login and password to get an admin account for geonetwork ?

#34 Updated by Nathan Vaughan 12 months ago

I can get the shiny app wrapped up in a docker as soon as it is ready.

#35 Updated by Fabio Sinibaldi 12 months ago

@julien.barde@ird.fr
Currently you can gather credentials by calling this address (specifying your gcube-token): https://sdi-d4s.d4science.org/sdi-service/gcube/service/SDI?gcube-token=

The geonetwork-connector component we are going to release in a couple of weeks should let the portal automatically login the user according to his VRE role. In the meantime, since directly calling the sdi-service might be disorienting for a simple user, I ask @massimiliano.assante@isti.cnr.it if a link to the above address could be provided from inside the portal.

#37 Updated by Julien Barde 12 months ago

Thanks @nathan.vaughan1@gmail.com , @anne.elise.nieblas@gmail.com will provide the code for the shiny app. Do you want her code to be made available through a Github repository ?

#38 Updated by Nathan Vaughan 12 months ago

Thanks @julien.barde@ird.fr yes github is the best way to share it.

#40 Updated by Anne Elise Nieblas 11 months ago

Hi @nathan.vaughan1@gmail.com (fyi: @julien.barde@ird.fr), the github repository is up for the IOTC_SS3 shiny to dockerize. Please let me know if you have any questions.

https://github.com/aenieblas/IOTC_SS3_Shiny

#41 Updated by Nathan Vaughan 11 months ago

Thanks @anne.elise.nieblas@gmail.com That github only seems to have the supporting documents for the shiny app not the app itself. The dockerizing creates an entire linux virtual machine that includes the shiny app and everything required for it so I need the whole app in one github. Here is an example https://github.com/nathanvaughan1/shinyproxy-BFT-E
For this @julien.barde@ird.fr provided everything inside the BFT folder and I cloned that, configured the dockerfile, then built the docker image to supply to @andrea.dellamico@isti.cnr.it for hosting on the VRE. Cheers,
Nathan

#42 Updated by Anne Elise Nieblas 11 months ago

Hi @nathan.vaughan1@gmail.com , thanks for your reply. Everything that is needed to run the shiny is there - I used the flexdashboard package to create the shiny, so the app is embedded in the shiny_dashboard_final.Rmd file. Will this be a problem?

#43 Updated by Nathan Vaughan 11 months ago

Thanks @anne.elise.nieblas@gmail.com I will take a look at it and let you know. I'm not sure if shiny proxy will have an issue identifying the app or not. We will find out :)

#44 Updated by Anne Elise Nieblas 11 months ago

@nathan.vaughan1@gmail.com Hi Nathan, just to let you know that I've updated the scripts on github (https://github.com/aenieblas/IOTC_SS3_Shiny) so that I could publish them on shinyapps.io (https://anne-elise-nieblas.shinyapps.io/ss3_dashboard_final/). I'm working on some issues (specifically to read the data using OPeNDAP instead of locally hosting the data files), and expect to have another version to you in the coming days, but I'd really like to have a test on whether the shiny dockerizes - because if it does, I'd like to showcase it at an upcoming meeting. Thanks! Anne-Elise

#45 Updated by Nathan Vaughan 11 months ago

@anne.elise.nieblas@gmail.com and @andrea.dellamico@isti.cnr.it

Hi Anne, I have compiled the previous version of the app on dockerhub. Andrea, could you try hosting to see if it works with the R markdown file. Here are the details for the app Andrea which is on docker hub now. We can update the app version once you have all the bugs sorted.

name: IOTC_SS3

display-name: IOTC_SS3 shiny app

docker-cmd: ["R", "-e rmarkdown::render('/root/IOTC_SS3/ss3_dashboard_final.rmd')"]

docker-image: nathanvaughan/shinyproxy-iotc_ss3

#46 Updated by Andrea Dell'Amico 11 months ago

Nathan Vaughan wrote:

Hi Anne, I have compiled the previous version of the app on dockerhub. Andrea, could you try hosting to see if it works with the R markdown file. Here are the details for the app Andrea which is on docker hub now. We can update the app version once you have all the bugs sorted.

docker-cmd: ["R", "-e rmarkdown::render('/root/IOTC_SS3/ss3_dashboard_final.rmd')"]

@nathan.vaughan1@gmail.com something is wrong with the command line, the path does not exist. The container fails to start with the following error:

 > rmarkdown::render('/root/IOTC_SS3/ss3_dashboard_final.rmd')
 Error in tools::file_path_as_absolute(input) :
   file '/root/IOTC_SS3/ss3_dashboard_final.rmd' does not exist
 Calls: <Anonymous> -> setwd -> dirname -> <Anonymous>
 In addition: Warning message:
 In normalizePath(path, winslash = winslash, mustWork = mustWork) :
   path[1]="/root/IOTC_SS3/ss3_dashboard_final.rmd": No such file or directory
 Execution halted

#47 Updated by Nathan Vaughan 11 months ago

Thanks for the quick turn around @andrea.dellamico@isti.cnr.it I try to figure out if this is a simple error of mine or if shiny proxy is having an issue with the rmd file.

#48 Updated by Nathan Vaughan 11 months ago

@andrea.dellamico@isti.cnr.it I have updated the docker build to fix the file not found issue appears to be a markdown bug. Let me know how it goes, there are apparently bugs with the rmarkdown::run command related to accessing external data but this is the only one that may work. Here are the new shiny proxy details too

name: IOTC_SS3
display-name: IOTC_SS3 shiny app
docker-cmd: ["R", "-e rmarkdown::run('/root/IOTC_SS3/ss3_dashboard_final.Rmd')"]
docker-image: nathanvaughan/shinyproxy-iotc_ss3

#49 Updated by Andrea Dell'Amico 11 months ago

Now the container starts, but the app fails. It seems that a package is missing:

Warning: Error in loadNamespace: there is no package called ‘flexdashboard’
 Stack trace (innermost first):
     111: <Anonymous>
     110: stop
     109: value[[3L]]
     108: tryCatchOne
     107: tryCatchList
     106: tryCatch
     105: getNamespace
     104: asNamespace
     103: getExportedValue
     102: ::
     101: eval
     100: eval
      99: create_output_format
      98: <Anonymous>
      97: do.call
      96: contextFunc
      95: .getReactiveEnvironment()$runWith
      94: shiny::maskReactiveContext
      93: <reactive>
      82: doc
      81: shiny::renderUI
      80: func
      79: origRenderFunc
      78: output$__reactivedoc__
       3: <Anonymous>
       2: do.call
       1: rmarkdown::run

#50 Updated by Nathan Vaughan 11 months ago

@andrea.dellamico@isti.cnr.it added flexdashboard and the build is updated now.

#51 Updated by Andrea Dell'Amico 11 months ago

The missing package is now plotly. If I read the source well here https://github.com/aenieblas/IOTC_SS3_Shiny/blob/master/ss3_dashboard_final.Rmd it's also the last requirement, so no other one should be missing.

#52 Updated by Nathan Vaughan 11 months ago

Sorry @andrea.dellamico@isti.cnr.it looks like I mistakenly overwrote the code where I originally added these packages. Should be good to go now.

#53 Updated by Nathan Vaughan 11 months ago

Thanks @andrea.dellamico@isti.cnr.it looks like the app is up and running now. @anne.elise.nieblas@gmail.com and @julien.barde@ird.fr you can access the app at https://shinyproxy.d4science.org/app/IOTC_SS3

#54 Updated by Julien Barde 11 months ago

thank you @nathan.vaughan1@gmail.com and @andrea.dellamico@isti.cnr.it
The application works fine (but there is a bug to be fixed on our side). We will provide a new version soon.

#55 Updated by Anne Elise Nieblas 11 months ago

hello! thanks @nathan.vaughan1@gmail.com and @andrea.dellamico@isti.cnr.it - the app looks great! i've made some changes to the code to sort out the bugs. the final codes can be found here on github: https://github.com/aenieblas/IOTC_SS3_Shiny.git

Would it be possible to change the title of the app from "IOTC_SS3" to "SS3 Diagnostic Plots"?

Final question - how does it work to update the app when new data/model runs become available? Currently, the shiny reads data from the Thredds server : http://mdst-macroes.ird.fr:8080/thredds/dodsC/BlueBridge/IOTC/catalog.html, but it also needs to read an additional file "../data/run_spec_ss3.csv" in order to inform bits of the script. Updating the Thredds server is no problem from our side, but how do I update the .csv file? Will I have to send you the file to update the app every time more runs are added?

Thanks for your help!

#56 Updated by Pasquale Pagano 11 months ago

I am not a Shiny expert and so I am not sure my answers and suggestions fit well. However please consider the follow.

Final question - how does it work to update the app when new data/model runs become available? Currently, the shiny reads data from the Thredds server : http://mdst-macroes.ird.fr:8080/thredds/dodsC/BlueBridge/IOTC/catalog.html, but it also needs to read an additional file "../data/run_spec_ss3.csv" in order to inform bits of the script.
Updating the Thredds server is no problem from our side,

Why are you not using the Thredds server offered by the infrastructure?

but how do I update the .csv file? Will I have to send you the file to update the app every time more runs are added?

You could store the csv in the VRE workspace. Then you could use the persistent public URL to get it in your application. When you will need to update it, you will update the file on the workspace. The new version of the file will maintain the same URL while your application will download the correct version. Is this sound for you?

#57 Updated by Julien Barde 11 months ago

thanks @pasquale.pagano@isti.cnr.it
We use our own Thredds since the synchronization of WS folder with Thredds is not easy at this stage in the infra: we can't remove or replace a folder or files within the folder without a human doing it for us and we were in the middle of a process where it was needed multiple times a day (it's been discussed with @fabio.sinibaldi@isti.cnr.it). That was much more flexible then but we are waiting for the infra to be able to manage the Thredds server just like a normal one.

You are right for the CSV, this is how it should be done (download rather than embedded in the app): is there a special trick to do this from shiny proxy or is it possible "as usual" : in this case by using @anne.elise.nieblas@gmail.com "user_name" and "token" ?

We presented the work last week at IOTC and we needed a first version to be deployed and discussed by the users. Now we will improve it.

#58 Updated by Pasquale Pagano 11 months ago

Julien Barde wrote:

thanks @pasquale.pagano@isti.cnr.it
We use our own Thredds since the synchronization of WS folder with Thredds is not easy at this stage in the infra: we can't remove or replace a folder or files within the folder without a human doing it for us and we were in the middle of a process where it was needed multiple times a day (it's been discussed with @fabio.sinibaldi@isti.cnr.it). That was much more flexible then but we are waiting for the infra to be able to manage the Thredds server just like a normal one.

Ok, understood.

You are right for the CSV, this is how it should be done (download rather than embedded in the app): is there a special trick to do this from shiny proxy or is it possible "as usual" : in this case by using @anne.elise.nieblas@gmail.com "user_name" and "token" ?

I was proposing to use a Public Link, like this one http://data.d4science.org/cTJOeFMrQVBQSWRxeGhqK1JWdzM5Q2ZXSjFWa1A4QTBHbWJQNStIS0N6Yz0 (just a file from the BB VRE workspace). It does not require the token to be consumed and you can download it with a wget or equivalent.

We presented the work last week at IOTC and we needed a first version to be deployed and discussed by the users. Now we will improve it.

#59 Updated by Julien Barde 11 months ago

ok thanks, we will use this kind of link with @anne.elise.nieblas@gmail.com
For your information, we plan to access the data remotely with OPeNDAP & NetCDF files on the Thredds server. It means that only the URL of the Thredds server (or catalog) would change in the code if it works as expected. It might become an input parameter at some point. But we still face issues at this stage.

#60 Updated by Nathan Vaughan 11 months ago

@andrea.dellamico@isti.cnr.it I have updated the docker image with @anne.elise.nieblas@gmail.com new code. I agree with previous comments that if you have data that needs to be updated periodically it would be best to have this hosted outside the app or allow for the user to upload the data.

#61 Updated by Andrea Dell'Amico 11 months ago

I just pulled the new image and changed the app name.

#62 Updated by Anne Elise Nieblas 11 months ago

Hello, I've updated the github scripts so that the .csv is read by accessing the public link. Thanks, Anne-Elise

#63 Updated by Nathan Vaughan 11 months ago

@andrea.dellamico@isti.cnr.it I've updated the docker image with @anne.elise.nieblas@gmail.com new code. Can you pull the new image, I think Anne may need it for a demo tomorrow.

#64 Updated by Andrea Dell'Amico 11 months ago

Done some minutes ago.

#65 Updated by Massimiliano Assante 10 months ago

  • Status changed from Available to Released

Also available in: Atom PDF