Skip to content

April 7, 2017, Friday

Liya Wang edited this page May 2, 2017 · 1 revision
  • Without logging in
    • Job submission is not working (history grey out)
    • History will be cleaned out once log in or log out
    • Making a decision that user can not launch job without logging in
  • Warning/confirmation on trying to launch job
    • With log in, show a pop-up window for confirmation (Yes, No button): "You are going to submit 1 (n) jobs to a cloud cluster, are you sure you want to launch it (them)?"
    • Without log in, submit button is greyed out with a hint message: "You need to sign in with your CyVerse credentials to launch a job!"
  • RNAseq workflow
    • Delete RNAseq and Chipseq for now
    • Data too big!
    • Might be suitable for de.sciapps.org (define a corresponding system with TACC's resources server for intermediate results)
    • Hold on for now, start 2018 on de.sciapps.org
  • History panel optimization (ignore for now)
    • If in database, not need to interact with Agave
    • Only load defined outputs in apps json
    • With such set up, job item can be constructed with job id (workflow json) and app json without consulting Agave
  • Front page re-design
    • Add a diagram to illustrate the backend system
    • Add description to explain the federation system and workflow advantages
    • Move building workflow instructions to help (new)
    • How do we display a Agave maintenance notification on the front page? Automatically pull from XML feed (use the feed for Agave servers)
Clone this wiki locally