<div dir="ltr"><div><div><div><div><div>I don't think event lists should be classified as <i>non-pixelated</i>.<br></div>If we want to model data consistently, they should be classified as <i>pixel lists</i>:<br>each event is a pixel; we just end up with a sparse hypercube.<br></div>If we were to add one more parameter: the total number of pixels in<br></div>the data product, that would solve the problem. For solid cubes it<br></div>would be the product of the *dims, for event lists the number of events.<br><br></div> - Arnold<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">-------------------------------------------------------------------------------------------------------------<br>Arnold H. Rots Chandra X-ray Science Center<br>Smithsonian Astrophysical Observatory tel: +1 617 496 7701<br>60 Garden Street, MS 67 fax: +1 617 495 7356<br>Cambridge, MA 02138 <a href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a><br>USA <a href="http://hea-www.harvard.edu/~arots/" target="_blank">http://hea-www.harvard.edu/~arots/</a><br>--------------------------------------------------------------------------------------------------------------<br><br></div></div></div>
<br><div class="gmail_quote">On Mon, Oct 5, 2015 at 11:00 AM, Laurent Michel <span dir="ltr"><<a href="mailto:laurent.michel@astro.unistra.fr" target="_blank">laurent.michel@astro.unistra.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
A consensus seems to be taking shape about the model evolution for pixelated data:<br>
+ Adding several fields to provide the dimensionality in each domain. (s_dim, em_dim, etc) as described in the draft<br>
+ These are added as 'required' fields.. so must be populated for all records<br>
+ These fields provide for instance the size of each image axis.<br>
<br>
These new fields can however not be used to provide a robust representation the dimension of non pixelated data (e.g. number of event in an event list)<br>
<br>
The proposal to complete the version would be:<br>
1) To keep the new *dim* fields<br>
2) To support the EventList and other non pixelated as product_type<br>
3) To clearly specify that the *dim* columns must be set with NaN for non pixelated data.<br>
4) To provide some use cases about discovering non pixelated data with ObsTap<br>
<br>
That would quiclky allow us to start the RFC period for ObsCore without having to wait on a agreement about how to model non pixelated data<br>
<br>
<br>
Laurent<br>
<br>
-- <br>
jesuischarlie<br>
<br>
Laurent Michel<br>
SSC XMM-Newton<br>
Tél : <a href="tel:%2B33%20%280%293%2068%2085%2024%2037" value="+33368852437" target="_blank">+33 (0)3 68 85 24 37</a><br>
Fax : +33 (0)3 )3 68 85 24 32<br>
<a href="mailto:laurent.michel@astro.unistra.fr" target="_blank">laurent.michel@astro.unistra.fr</a> <mailto:<a href="mailto:laurent.michel@astro.unistra.fr" target="_blank">laurent.michel@astro.unistra.fr</a>><br>
Université de Strasbourg <<a href="http://www.unistra.fr" rel="noreferrer" target="_blank">http://www.unistra.fr</a>><br>
Observatoire Astronomique<br>
11 Rue de l'Université<br>
F - 67200 Strasbourg<br>
<a href="http://amwdb.u-strasbg.fr/HighEnergy/spip.php?rubrique34" rel="noreferrer" target="_blank">http://amwdb.u-strasbg.fr/HighEnergy/spip.php?rubrique34</a><br>
</blockquote></div><br></div>