Difference between revisions of "User:Jmandel/WRF-Fire VisTrails wishlist"

From openwfm
Jump to navigation Jump to search
m (format)
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
==Summary==
 +
At the teleconference June 24 2010, we have agreed that
 +
* SCI will keep the information what exactly to do and where the files are as howtos on the wiki
 +
* SCI will output a NetCDF file with only the arrays as processed for visualization, for diagnostic purposes
 +
* UCD will communicate requirements for a custom visualization tool using VisTrails and CrowdLabs
 +
 
==Jan's wishlist==
 
==Jan's wishlist==
−
# up-to-date "How to visualize WRF-Fire output in VisTrails" at openwfm.org, working and clear enough for a clueless impatient prospective user
 
−
# a command line utility to reduce the wrfout files by leaving only the variables needed (a simple python script would do; I did not try to set up the server yet.)
 
−
# up to date .vt and package files and the above utility available in a publicly accessible git repository, also downoladable as a tarball or separately
 
−
# in vistrails, input the directories by navigating to them in the usual fashion as all other mac programs, but leave the option to type/cut/paste if possible
 
−
# a box with an error message should pop up if something is wrong with the path or the files
 
−
# the vistrails window should remain responsive during the conversion, show a progress bar and a cancel button, not just freeze up
 
−
# a box with an error message should pop up if something goes wrong with the conversion
 
−
# there should be some sort of altert (a dialog box in front?) when the conversion is done. I need to do other things while it is working and the vistrails window gets buried somewhere
 
−
# the "Fire demo visualization" should already know where the vtk files are, not ask again (or it should prefill the choice with the known location)
 
−
# make it simple to recover or backtrack when something goes wrong, including wrong user input. Make every step guaranteed re-runnable. I had to start from the scratch (exist vistrails, start again...) every single time when I messed up, which was quite often.
 
−
# Why all those boxes? A scientist probably does not care about the details, certainly not the first time. Just show the user one big button, the user will push the button, navigate to the directory with the wrfout files, watch the progress bar for a while, and then watch the movie. Or at most two buttons (convert, visualize), and make it clear in some dialog box or in the howto how to save and visualize the next time without converting again.
 
−
# There should be online help, or a help button to start the preview of the pdf of the manual. The pdf should be installed in the VisTrails application directory, where VisTrails.app is.
 
−
# it needs to be clear how to start a spreadsheet. The spreadsheet should pop up and not hide under the vistrails window.
 
−
# the axes in the visualization should be labeled and the current time displayed in every frame, please.
 
−
# The control buttons on the bottom should give some feedback when pressed. The movie reacts slowly (or not at all at times), so it is not clear what is happening
 
−
# The user interface is a bit raw and doing strange things at times. The look and feel should be the same as other native Mac applications. Probably VisTrails is not using the right Mac library for the GUI?
 
−
# The GUI should be really simplified to get the user hooked the first time: simple useful things should be done in a simple way, without studying anything. Then, if someone wants to get deeper, they can do that later.
 
−
# The Howto should say how to save the movie as a file.
 
−
# I'd like to display the heat flux instead of/in addition to the area burned (I think that's what vistrails displays now). Please see the attached pictures. (This is from a new feature, ignition points moving along lines over time.) Vistrails has some artefacts but I know do not have the current version of the files. Will retest after I get it.
 
−
# It would be good to have some usual options, best from drop-down menus, such as: selection of variables, colors, transparency, start/stop time, play in a loop or not, add legends, labels, colorbars,  etc.
 
−
# I could not find controls for rewind/advance and start/stop capture to a movie file.
 
−
# I can see the ultimate goal may include the server in a kiosk mode, with the user just pushing buttons and choosing from menus, with all the details of the internal working and anything the user could mess up hidden and disabled?
 
−
# What is animation delay, please?
 
−
# I would be nice if the controls are not be visible in captured images/movies.
 
  
−
==Jan's difficulties==
+
===Easy start===
−
# the only howto I found was [[How_to_run_the_Supercomputing_2009_WRF-Fire/Vistrails_demo]]
+
I think the following would really help to make it easier for a user (especially a novice) to take advantage of the software.
−
# In the absence of an up to date howto I was not sure which package files to use. I have left whatever was in my vistrails installation from the last time.
+
# up-to-date at least the first part of [[How to visualize WRF-Fire output in VisTrails]] (before the server), good even for a novice, and noting specific versions known to work
−
# I was not sure which .vt file to use because the howto is out of date. I have tried vt_files/fireDemoSC2009.new.vt from ssh://math.ucdenver.edu/home/grads/jbeezley/wrf_vistrails.git, which gave me the error "Pipeline cannot be instantiated: Missing package: edu.cudenver.jbeezley.namelist".
+
# all up to date files (anything extra that is not in stock VisTrails distribution) identified and publicly accessible (git repository, tarballs, package files in vistrails, crowdlabs), explained in the Howto, keep track of versions
−
# So I used VisTrails/scDemo2009/fireDemoSC2009running.vt file dated 2/26/10 which I had from some earlier attempt.
+
 
−
# during the conversion, vistrails seemed to disable other windows or steal focus from them (Chrome, in particular, where I am writing this)
+
===Creating visualization===
−
# After the conversion, the vtk were nowhere to be found (I did not create the directory, but Vistrains did not complain and just went ahead with the conversion?)
+
* Tell SCI folks which arrays to support
−
# it was not clear what exactly it means "View the spread sheet to interact with the visualization" in the howto. I forgot since the last time. There is no button labeled "spreadsheet". The manual says something about main menu or spreadsheet toolbar but I did not see any such things in the vistrails window either. I was afraid to try and
+
* SCI will build a custom visualization too, requires close communication
−
push random buttons for fear I would get to some state I could not recover from, and I would have to start all over again (another hour or so). Eventually, I accidentally found the spreadsheet hiding under the vistrails window.
+
* Wiki how to use kept up to date
 +
* Long-term solution
 +
* Need howto should be for someone who has fresh installation
 +
* VisTrails will dump also the NetCDF file with arrays that actually are visualized (and no others, to compress size) and the computed atmospheric nodes elevations. We'll use those files for input to Matlab and VAPOR for diagnostics.  It would be good if the generated netcdf file is compatible with the wrfout file and can be used as the VisTrails input instead of wrfout.
 +
 
 +
===Other===
 +
* [[User:Jmandel/WRF-Vistrails user interface suggestions|User interface suggestions]]
 +
* [[User:Jmandel/WRF-Fire-Vistrails difficulties|Difficulty finding the right files]]
  
 
==Jon's ideas==
 
==Jon's ideas==
−
Jon had in mind a couple of ideas that could help with usability and development.
+
A couple of ideas that could help with usability and development.
  
−
==Configuration parameters==
+
===Configuration parameters===
  
 
Trying to customize a simulation by setting defaults for input ports is awkward and becomes almost impossible to manage when there is a large number of options in a workflow.  I'm wondering if it would be possible to make some sort of a default configuration dialog that would pop up when running a workflow.  Something like a standard configuration widget that contains all unconnected input ports that you can see and modify in one place.
 
Trying to customize a simulation by setting defaults for input ports is awkward and becomes almost impossible to manage when there is a large number of options in a workflow.  I'm wondering if it would be possible to make some sort of a default configuration dialog that would pop up when running a workflow.  Something like a standard configuration widget that contains all unconnected input ports that you can see and modify in one place.
Line 44: Line 33:
 
Even better would be something like a module that you can place in the workflow with one output port.  When you connect the output port to an input with a basic class (float/int/file/bool, etc.) that input is added to the configuration dialog with an appropriate gui element (for files, a string input with a button for opening a file dialog, etc.).  Maybe multiple configuration boxes in the workflow could create individual tabs in the dialog.
 
Even better would be something like a module that you can place in the workflow with one output port.  When you connect the output port to an input with a basic class (float/int/file/bool, etc.) that input is added to the configuration dialog with an appropriate gui element (for files, a string input with a button for opening a file dialog, etc.).  Maybe multiple configuration boxes in the workflow could create individual tabs in the dialog.
  
−
==Subworkflows==
+
===Subworkflows===
  
 
The problem with the workflow containing too many boxes is it becomes overcomplicated both to understand what it is really doing and to find what it is you are looking for.  I'm aware that there is support for grouping of boxes and subworkflows; however, the problem with this approach is that all of the input/output ports get combined into a single box and (as far as I can tell) there is no way to figure out what each port does.  Perhaps a way to annotate ports would help.
 
The problem with the workflow containing too many boxes is it becomes overcomplicated both to understand what it is really doing and to find what it is you are looking for.  I'm aware that there is support for grouping of boxes and subworkflows; however, the problem with this approach is that all of the input/output ports get combined into a single box and (as far as I can tell) there is no way to figure out what each port does.  Perhaps a way to annotate ports would help.

Latest revision as of 08:44, 25 June 2010

Summary

At the teleconference June 24 2010, we have agreed that

  • SCI will keep the information what exactly to do and where the files are as howtos on the wiki
  • SCI will output a NetCDF file with only the arrays as processed for visualization, for diagnostic purposes
  • UCD will communicate requirements for a custom visualization tool using VisTrails and CrowdLabs

Jan's wishlist

Easy start

I think the following would really help to make it easier for a user (especially a novice) to take advantage of the software.

  1. up-to-date at least the first part of How to visualize WRF-Fire output in VisTrails (before the server), good even for a novice, and noting specific versions known to work
  2. all up to date files (anything extra that is not in stock VisTrails distribution) identified and publicly accessible (git repository, tarballs, package files in vistrails, crowdlabs), explained in the Howto, keep track of versions

Creating visualization

  • Tell SCI folks which arrays to support
  • SCI will build a custom visualization too, requires close communication
  • Wiki how to use kept up to date
  • Long-term solution
  • Need howto should be for someone who has fresh installation
  • VisTrails will dump also the NetCDF file with arrays that actually are visualized (and no others, to compress size) and the computed atmospheric nodes elevations. We'll use those files for input to Matlab and VAPOR for diagnostics. It would be good if the generated netcdf file is compatible with the wrfout file and can be used as the VisTrails input instead of wrfout.

Other

Jon's ideas

A couple of ideas that could help with usability and development.

Configuration parameters

Trying to customize a simulation by setting defaults for input ports is awkward and becomes almost impossible to manage when there is a large number of options in a workflow. I'm wondering if it would be possible to make some sort of a default configuration dialog that would pop up when running a workflow. Something like a standard configuration widget that contains all unconnected input ports that you can see and modify in one place.

Even better would be something like a module that you can place in the workflow with one output port. When you connect the output port to an input with a basic class (float/int/file/bool, etc.) that input is added to the configuration dialog with an appropriate gui element (for files, a string input with a button for opening a file dialog, etc.). Maybe multiple configuration boxes in the workflow could create individual tabs in the dialog.

Subworkflows

The problem with the workflow containing too many boxes is it becomes overcomplicated both to understand what it is really doing and to find what it is you are looking for. I'm aware that there is support for grouping of boxes and subworkflows; however, the problem with this approach is that all of the input/output ports get combined into a single box and (as far as I can tell) there is no way to figure out what each port does. Perhaps a way to annotate ports would help.

Retrieved from "http://wiki.openwfm.org/mediawiki/index.php?title=User:Jmandel/WRF-Fire_VisTrails_wishlist&oldid=1052"