[Nexus-developers] NeXus-2010 workshop
Carlos Pascual Izarra
carlos.pascual at cells.es
Tue May 18 16:42:28 BST 2010
On Tue May 18 2010 15:32:39 freddie.akeroyd at stfc.ac.uk wrote:
> 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.
Actually, the name we used originally was NXApplication, but after some debate
we considered that the class was actually just the same as an NXentry (only
that it was within an NXentry). Hence NXsubentry.
But I think everybody in the group who made the proposal would agree in that
the name is non-important as long as the functionality is provided.
>
> 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?
We didn't think about that, but I find it feature since it solves the main
problem that would be present otherwise: choosing a syntax for defining
mathematical operations and describing how it should be interpreted by the
data consumer. If the conversion is handled by the NAPI, there would be no
room for implementation discrepancies.
Cheers!
--
+----------------------------------------------------+
Carlos Pascual Izarra
Scientific Software Contact
Computing Division
Cells / Alba Synchrotron [http:/www.cells.es]
Carretera BP 1413 de Cerdanyola-Sant Cugat, Km. 3.3
E-08290 Cerdanyola del Valles (Barcelona), Spain
E-mail: carlos.pascual at cells.es
Phone: +34 93 592 4428
+----------------------------------------------------+
More information about the NeXus-developers
mailing list