User:Jmandel/WRF-Fire VisTrails wishlist - Revision history

Jmandel: /* Summary */

2010-06-25T08:44:16Z

Summary

← Older revision		Revision as of 08:44, 25 June 2010
Line 3:		Line 3:
	* SCI will keep the information what exactly to do and where the files are as howtos on the wiki		* 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		* SCI will output a NetCDF file with only the arrays as processed for visualization, for diagnostic purposes
	* ~~both~~ will communicate ~~closely and promptly about~~ requirements for a custom visualization tool using VisTrails and CrowdLabs		* UCD will communicate requirements for a custom visualization tool using VisTrails and CrowdLabs

	==Jan's wishlist==		==Jan's wishlist==

Jmandel: /* Summary */

2010-06-24T22:23:54Z

Summary

← Older revision		Revision as of 22:23, 24 June 2010
Line 2:		Line 2:
	At the teleconference June 24 2010, we have agreed that		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 keep the information what exactly to do and where the files are as howtos on the wiki
	* SCI will output a NetCDF file with ~~all~~ arrays as processed for visualization ~~(an no others)~~ for ~~diagnostics~~		* SCI will output a NetCDF file with only the arrays as processed for visualization, for diagnostic purposes
	* both will communicate closely and promptly about requirements for a custom visualization tool using VisTrails and CrowdLabs		* both will communicate closely and promptly about requirements for a custom visualization tool using VisTrails and CrowdLabs

Jmandel: /* Summary */

2010-06-24T22:23:03Z

Summary

← Older revision		Revision as of 22:23, 24 June 2010
Line 2:		Line 2:
	At the teleconference June 24 2010, we have agreed that		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 keep the information what exactly to do and where the files are as howtos on the wiki
	* SCI output a NetCDF file with all arrays as processed for visualization (an no others) for diagnostics		* SCI will output a NetCDF file with all arrays as processed for visualization (an no others) for diagnostics
	* both will communicate closely and promptly about requirements for a custom visualization tool using VisTrails and CrowdLabs		* both will communicate closely and promptly about requirements for a custom visualization tool using VisTrails and CrowdLabs

Jmandel: /* Summary */

2010-06-24T22:22:49Z

Summary

← Older revision		Revision as of 22:22, 24 June 2010
Line 1:		Line 1:
	==Summary==		==Summary==
	At the teleconference June 2010, we have agreed to		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 keep the information what exactly to do and where the files are as howtos on the wiki
	* SCI output a NetCDF file with all arrays as processed for visualization (an no others) for diagnostics		* SCI output a NetCDF file with all arrays as processed for visualization (an no others) for diagnostics

Jmandel: summary

2010-06-24T22:21:34Z

summary

← Older revision		Revision as of 22:21, 24 June 2010
Line 1:		Line 1:
			==Summary==
			At the teleconference June 2010, we have agreed to
			* SCI will keep the information what exactly to do and where the files are as howtos on the wiki
			* SCI output a NetCDF file with all arrays as processed for visualization (an no others) for diagnostics
			* both will communicate closely and promptly about requirements for a custom visualization tool using VisTrails and CrowdLabs

	==Jan's wishlist==		==Jan's wishlist==

Line 11:		Line 17:
	* Wiki how to use kept up to date		* Wiki how to use kept up to date
	* Long-term solution		* Long-term solution
	* ~~Howto~~ should be for someone who has fresh installation		* 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.		* 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.

Jmandel: /* Easy start */

2010-06-24T21:29:20Z

Easy start

← Older revision		Revision as of 21:29, 24 June 2010
Line 2:		Line 2:

	===Easy start===		===Easy start===
	I think the following would really help to make it easier for a user to ~~use~~ the software.		I think the following would really help to make it easier for a user (especially a novice) to take advantage of the software.
	# 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		# 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
	# 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		# 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

Jmandel: /* Creating visualization */

2010-06-24T21:26:47Z

Creating visualization

← Older revision		Revision as of 21:26, 24 June 2010
Line 12:		Line 12:
	* Long-term solution		* Long-term solution
	* Howto should be for someone who has fresh installation		* 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 ~~the~~ 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.		* 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===		===Other===

Jmandel: /* Creating visualization */

2010-06-24T21:25:49Z

Creating visualization

← Older revision		Revision as of 21:25, 24 June 2010
Line 12:		Line 12:
	* Long-term solution		* Long-term solution
	* Howto should be for someone who has fresh installation		* 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 ~~compute~~ the atmospheric ~~node elevation~~. We'll use those as input to Matlab and VAPOR for diagnostics. It would be good if the file is compatible with the wrfout file to be used as the VisTrails input		* VisTrails will dump also the NetCDF file with arrays that actually are visualized (and no others, to compress size) and the computed the 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===		===Other===

Jmandel at 21:24, 24 June 2010

2010-06-24T21:24:26Z

@@ Line 12: / Line 12: @@
 * Long-term solution
 * 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 compute the atmospheric node elevation. We'll use those as input to Matlab and VAPOR for diagnostics.  It would be good if the file is compatible with the wrfout file to be used as the VisTrails input
 ===Other===

Jmandel: /* Fine grained workflow and NetCDF utilities */

2010-06-24T21:19:27Z

Fine grained workflow and NetCDF utilities

← Older revision		Revision as of 21:19, 24 June 2010
Line 15:		Line 15:
	===Fine grained workflow and NetCDF utilities===		===Fine grained workflow and NetCDF utilities===

			VisTrails will dump also NetCDF files.
	This is a natural for a VisTrails workflow. But I need standalone command line versions of the utilities also, to be included in the WRF-Fire repository, which does not depend on VisTrails. The format of the intermediate files should be NetCDF so that the files can be easily manipulated by other software we have, in particular examined in Matlab.		This is a natural for a VisTrails workflow. But I need standalone command line versions of the utilities also, to be included in the WRF-Fire repository, which does not depend on VisTrails. The format of the intermediate files should be NetCDF so that the files can be easily manipulated by other software we have, in particular examined in Matlab.