<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Please be careful to fully consider the situation, Armando!<br>
You are asking for a default plot - Ray is saying that the
description of that "default" plot shouldn't have arbitrary limits
and that this might make it too complicated to be practical.<br>
In order to provide new options to specify default plots beyond what
is currently provided by NeXus, we are discussing changes that have
consequences beyond the use-case you are using as an example.
Therefore, your answer to Ray of "Nobody is asking for it" is not
really true. Many of us who use NeXus will not be happy with a
change to NeXus that solves your issue without having enough
flexibility to also resolve other, similar issues and so the ability
to "specify all other possible non-default plots" is something we
*should* consider as part of the requested change as part of keeping
NeXus functioning well in the future. Please don't shut down such
discussion with dismissive statements - we all want to make NeXus
better.<br>
<br>
Cheers,<br>
Ben<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/01/18 15:40, V. Armando Solé
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:786a8e25-fedc-52a0-b60e-442b1b450eec@esrf.fr">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">On 11/01/2018 15:36, Osborn, Raymond
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:58E7FC59-6578-4C30-8705-EA8F0B627F34@anl.gov">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class=""> I saw the
Github issue and responded before I realized there was already
a lengthy correspondence here. I will have to read more
carefully what has already been contributed here, but I wanted
to quickly summarize what I wrote there (<a
href="https://github.com/nexusformat/NIAC/issues/25"
class="" moz-do-not-send="true">https://github.com/nexusformat/NIAC/issues/25</a>):
<div class=""><br class="">
</div>
<div class="">“In my view, it is the role of the NeXus
standard to provide a way to offer a default plot for each
NXdata group, but I don't think it is necessary for NeXus to
then specify all other possible non-default plots. Any
program is free to provide that option within the current
standard as NeXpy does.”</div>
<div class=""><br class="">
</div>
<div class="">Please see the issue for my reasoning -
basically, you can do what Armando requests, i.e., plot
multiple signals, now without adding extra complexity to the
standard.</div>
</div>
</blockquote>
<br>
The goal is not to foresee any possible plot. It is to provide a
default plot. I post the answer I sent to github here too:<br>
<br>
<div class="moz-text-plain" wrap="true" style="font-family:
-moz-fixed; font-size: 14px;" lang="x-unicode">
<pre wrap="">On 11/01/2018 15:04, Ray Osborn wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap="">To summarize - in my view, it is the role of the NeXus standard to
provide a way to offer a default plot for each NXdata group,
</pre>
</blockquote>
<pre wrap="">Exact, but to me the default plot for a fit is the raw_data, the used
uncertainties and the fitted curve.
NeXus provides everything for it except the possibility to put the
auxiliary curve.
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap="">but I don't think it is necessary for NeXus to then specify all other
possible non-default plots.
</pre>
</blockquote>
<pre wrap="">Nobody is asking for it.
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap="">Any program is free to provide that option within the current standard
as NeXpy does.
</pre>
</blockquote>
<pre wrap="">PyMca does it too, so that is not the problem. However, consider the
marvellous opportunity NeXus offers to provide the output of a fit (or
other treatments), with uncertainties, axis labels, and fitted curve at
the cost of defining two group attributes.
If NIAC tells me that Peter Chang's solution is not going to be
considered at all, it is fine with me too. We'll implement those two
attributes at our side and they will not conflict with any other
implementation.
</pre>
</div>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus">http://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
<br>
</body>
</html>