[NeXus-committee] Beam position monitors

[Pete Jemian]

A BPM has unique features that differentiate it from a 2D detector.  For
starters, it has no 2D image.  It has scaling information for each sensor
(the gain and offset of the current amplifiers, in the most common design),
each of which has a host of settings to be documented.  The various fields
and assumptions of NXdetector are a poor fit to describe BPMs.

On Nov 15, 2016 7:27 AM, "Benjamin Watts" <benjamin.watts at psi.ch> wrote:

> Hi Eugen,
>    A BPM is essentially a 2D detector and so it should follow NXdetector.
> In fact, wouldn't it make sense to just use NXdetector to represent a BMP?
>
> Cheers,
> Ben
>
>
>
> On 15/11/16 10:23, Eugen Wintersberger wrote:
>
> Hi folks,
>   I have currently a request for storing data from a beam position monitor
> within a NeXus file.
> As we currently have no base class to store such data and beam position
> monitors are rather common
> I made a small draft for a new base class NXbpm (see the attached PDF).
> It is currently in a very early stage. I guess the best approach would be
> that we try this at
> DESY and discuss this during the next NIAC meeting in two years.
>
> Can you guys please have a look on the draft and let me know if there are
> some things I have missed
> or if you have some good ideas about items to add or do differently?
>
> best regards
>    Eugen
>
> --
> Dr. Eugen Wintersberger
>
> FS-EC
> DESY
> Notkestr. 85
> D-22607 Hamburg
> Germany
>
>
> _______________________________________________
> NeXus-committee mailing listNeXus-committee at nexusformat.orghttp://lists.nexusformat.org/mailman/listinfo/nexus-committee
>
>
>
> _______________________________________________
> NeXus-committee mailing list
> NeXus-committee at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-committee
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/pipermail/nexus-committee/attachments/20161115/360c70e1/attachment.html>