2015 Summer Project Week:Astronomy - Revision history

Davide: /* Key Investigators */

2018-02-14T16:10:02Z

Key Investigators

2018-02-14T16:09:20Z

2018-02-14T16:08:34Z

2018-02-14T16:07:26Z

2018-02-14T16:06:48Z

2018-02-14T16:06:29Z

2018-02-14T16:06:07Z

2018-02-14T16:05:51Z

2018-02-14T16:05:15Z

2015-06-24T11:19:30Z

Project Description

@@ Line 6: / Line 6: @@
 ==Key Investigators==
 *Davide Punzo, Kapteyn Astronomical Institute, University of Groningen, Netherlands
-*anyone interested is very welcome
+*Steve Pieper, Isomics
 ==Project Description==

@@ Line 44: / Line 44: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Progress:  </h3>
 <h3>outcome from 1st day: coordinates, labels and units. </h3>
 *data probe coordinates: factorize getPixelString in the logic of the volumes and use the WCSlib in the logic of AstroVolume;
 *ruler widget: takes units properly -> OK;

@@ Line 40: / Line 40: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Approach, Plan</h3>
-* finish the first objective;
+* discuss the best approaches;
 </div>
 <div style="width: 27%; float: left; padding-right: 3%;">

@@ Line 45: / Line 45: @@
 <h3>Progress:  </h3>
 *VTK_FITS reader (and writer) and the Slicer AstroVolume module done; working on VTK_WCS_transformation.
 <h3>outcome from 1st day: coordinates, labels and units. </h3>

← Older revision		Revision as of 16:05, 14 February 2018
Line 49:		Line 49:


−		+	<h3> </h3>

	<h3>outcome from 1st day: coordinates, labels and units. </h3>		<h3>outcome from 1st day: coordinates, labels and units. </h3>

@@ Line 55: / Line 55: @@
 *ruler widget: takes units properly -> OK;
 *text on slices view: takes units properly -> OK;
-*"spacing annotation" (horizontal widget showing the physical spacing): problem, makeScalingRuler method is hardcoded with mm and cm. Moreover we'd like a different design (kvis example http://www.atnf.csiro.au/computing/software/karma/tool-screen-snapshots/kvis.gif ) -> is factoring the class vtkPVScalarBarActor in the logic of the volumes a solution?;
+*"spacing annotation" (horizontal widget showing the physical spacing): problem, makeScalingRuler method is hardcoded with mm and cm. Moreover we'd like a different design -> is factoring the class vtkPVScalarBarActor in the logic of the volumes a solution?;
 *units: we have different unit for the third axes and we have also units for flux (pixel intensity), how to handle these?;

@@ Line 66: / Line 66: @@
 <h3>outcome from 3rd day: </h3>
 *vtkMRMLAstroVolumeNode with *wcs struct integrated in SlicerAstro extension.
-*working on a engineering modifications to add a velocity and intensity quantities in the Units module.
+*working on modifications to the Units module for adding velocity and intensity quantities.
 *Engineering solutions for data probe and slice view annotations hardcoded features will be addressed after the Units module.