[Nexus] Correct way to specify multiple signals

[Benjamin Watts]

Please be careful to fully consider the situation, Armando!
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.
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.

Cheers,
Ben


On 11/01/18 15:40, V. Armando Solé wrote:
> On 11/01/2018 15:36, Osborn, Raymond wrote:
>> 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 
>> (https://github.com/nexusformat/NIAC/issues/25):
>>
>> “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.”
>>
>> 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.
>
> 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:
>
> On 11/01/2018 15:04, Ray Osborn wrote:
>> 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,
> 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.
>
>
>> but I don't think it is necessary for NeXus to then specify all other
>> possible non-default plots.
> Nobody is asking for it.
>
>> Any program is free to provide that option within the current standard
>> as NeXpy does.
> 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.
>
>
>
>
>
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/pipermail/nexus/attachments/20180111/c8b7c7d7/attachment-0001.html>