Skip to content

Latest commit

 

History

History
31 lines (18 loc) · 3.29 KB

monitor-the-app-package-generation-process.md

File metadata and controls

31 lines (18 loc) · 3.29 KB

Monitor the App Package Generation Process

View your Application Package in Dockstore to confirm that it was generated correctly. There is additional detail on how to use Dockstore in Gitbook in the Exploring the Application Catalog section.

  1. Go to Dockstore and you will see the webpage as shown in the figure below

  1. Search for your Application Package by either browsing the list of Available Workflows or using the Search box as shown below

  1. To check the status of the Application-package Generation, look at the Versions tab, as shown below. Currently there is no status-indicator that an Application Package is being generated; when it is done you should see a new Version of the Application Package show up in the list with a timestamp from a few minutes ago.

  1. Open up the details of your Application Package by clicking on the “Files” tab.

This will help explain what is in an OGC Application Package:

  • Dockstore.cwl: This is a boilerplate file needed for Dockstore.It tells the system what the main workflow execution file is
    • In this example, under the “step” section with the keyword “run”, the “workflow.cwl” will get executed.
  • process.cwl: This tells the system what the underlying executable is, plus inputs and outputs. In this case, it points at the process.ipynb noted in the "Clone the Example Application Code" section.
  • stage_in.cwl and stage_out.cwl: These are created by the Unity system to manage input- and output-data management.
  • workflow.cwl: This CWL file is the wrapper that captures the process.cwl, stage_in.cwl, and stage_out.cwl to be executed by Airflow. When executing the application within MDPS, as in this Tutorial, you will need to reference “workflow.cwl” as an input explained in a later section (Execute the App Package in SPS using Airflow).

\