[Nexus-developers] NeXus-2010 workshop

[freddie.akeroyd at stfc.ac.uk]

Hi Mark,

I'm glad you had a productive meeting. 

I agree with the idea of an NXsubentry (1.2.1), but I've been thinking
if this is the best name. As it is related to an "application or domain
specific definition" maybe the class name should reflect this? Something
along the lines of NXappdef, NXapplication, ... However the counter
argument is that application definitions already apply to NXentry so
calling it "NXsubentry" fits more with the current model. I was
wondering though if we were moving towards application definitions only
applying to "subentries" and not to "entries" themselves in which case
an NXappdef etc. class name could be a more appropriate.  

With regard to scaled data (1.2.2) were there any requests to add
utilities to the API to apply the scaling "on the fly" as the data was
read?

Regards,

Freddie


-----Original Message-----
From: nexus-developers-bounces at nexusformat.org
[mailto:nexus-developers-bounces at nexusformat.org] On Behalf Of Mark
Koennecke
Sent: 17 May 2010 16:23
To: nexus-developers at nexusformat.org
Subject: [Nexus-developers] NeXus-2010 workshop

Hi,

by now, the NeXus workshop at PSI has finished. Everything went
reasonably well, with the exception of a glitch in the python binding
which probably is due to an installation problem here. We had a couple
of quite lively and constructive discussions.
I attached a preliminary report for us to discuss on the Wednesday
teleconference. I would love it if we could come back to the community
with decisions about the major points raised soon.

Best Regards,

    Mark


-- 
Scanned by iCritical.