Draft standard : APT-HDF specifiction

[Daniel Haley]

Hi All,

At this point I would like to request any further discussion about the
initial draft for the HDF specification be brought forwards.

I will seek to have a community mail out that we have a draft in the
coming weeks, so if there are unresolved concerns in the current
document, please do raise them. I note there are still a few comment
threads that are still outstanding.

Thanks,

Daniel

[London, Andy]

We are missing some definition of multi-hits. I think previously we had suggested DetectorHitMultiplicity as a field entry. 

I suggest a 1xn field of ints to store the hit multiplicity (number of hits per pulse).

The EPOS method is to have [hit multiplicity] as the first hit, followed by a number of zeros equal to [hit multiplicity]-1:

[1 1 1 2 0 1 1 3 0 0 1 1]

Alternatively we could not include the zeros, like so:

[1 1 1 2 2 1 1 3 3 3 1 1]

While in theory it is possible to derive this directly from the pulse number of the hit, however, as most of this data will be 1's or 2's, it will be highly compressible within the HDF file and it will avoid users having to calculate it them selves.

Thoughts?

I think the geometry definition isn't well defined at the moment, does anyone have example on how one should determine this in practice? I think that would be helpful to drive the standard.

Andy

---

From: atompr...@googlegroups.com <atompr...@googlegroups.com> on behalf of Daniel Haley <daniel...@materials.ox.ac.uk>
Sent: 10 June 2020 23:12
To: atompr...@googlegroups.com <atompr...@googlegroups.com>
Subject: Draft standard : APT-HDF specifiction

 

--
You received this message because you are subscribed to the Google Groups "AtomProbe TC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atomprobe-tc...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/atomprobe-tc/63e658dd-8b52-a3a7-f278-182cd4c67df7%40materials.ox.ac.uk.