Hit amplitude not available when reading offline data

The hit amplitude obtained from the ToT for real data is not easily accessible (no hits.a attribute) @vpestel

added discussion label

For adding a bit of background, the amplitude a is now a property since the last km3net-dataformat (the release pre V6.00 version of the data processing).

I was not able to find back the info in a changelog, but now every hits has a filled with an amplitude computed from the tot with the PMT model available in JPP.

@tgal I think you've hidden this field, but it can now be accessed. Here is a small code snippet to access the property as an example (for Nikhef, I don't know where we have data file on sps ...):

import km3io as kio                                                                                                                                                                                                
                                                                                                                                                                                                                   
                                                                                                                                                                                                                   
fname = '/dcache/antares/detector_data/reconstructed/v6.00/KM3NeT_00000049/datav6.0.jorcarec.aanet.00008801.root'                                                                                                  
                                                                                                                                                                                                                   
f = kio.OfflineReader(fname)                                                                                                                                                                                       
t = f._fobj['E'].arrays(['hits.a'], library='ak')                                                                                                                                                                  
                                                                                                                                                                                                                   
print (t['hits.a'][0,:])                                                                                                                                                                                           

Also, from a direct file reading in ROOT:

root [1] E->Scan("hits.a")
***********************************
*    Row   * Instance *    hits.a *
***********************************
*        0 *        0 * 1.6695302 *
*        0 *        1 * 1.2389603 *
*        0 *        2 * 0.8285079 *
*        0 *        3 * 0.4115567 *
*        0 *        4 * 1.3755438 *
*        0 *        5 * 1.0097999 *
*        0 *        6 * 0.8285079 *
*        0 *        7 * 0.7524857 *
*        0 *        8 * 0.8285079 *
*        0 *        9 * 1.3755438 *
*        0 *       10 * 1.2389603 *
*        0 *       11 * 0.6847588 *
*        0 *       12 * 1.1176397 *
*        0 *       13 * 3.7678052 *
*        0 *       14 * 1.9648485 *
*        0 *       15 * 1.0097999 *
*        0 *       16 * 2.8590945 *
*        0 *       17 * 0.5226604 *
*        0 *       18 * 0.2547518 *
*        0 *       19 * 1.6695302 *
*        0 *       20 * 2.1129966 *
*        0 *       21 * 0.6244029 *
*        0 *       22 * 0.9138790 *
*        0 *       23 * 0.3596756 *
*        0 *       24 * 1.3755438 *

created merge request !64 (merged) to address this issue

mentioned in merge request !64 (merged)

I think I have solved it in !64 (merged)

Oh, I was not aware that we reintroduced this amplitude estimation. Is it based on @jreubelt's work?

I thought it was @bjjung's work, but not sure !

mentioned in commit e08cbe1b

closed with merge request !64 (merged)

created merge request !65 (merged) to address this issue

mentioned in merge request !65 (merged)

Sorry @tgal, I did a mistake in the previous merge request (mapped a to mc_hits.a, instead of hits.a). Corrected in: !65 (merged)

mentioned in commit b402f95d

All fine, thanks! It's merged to master and the release 0.24.0 is on the way to Lyon CC and PyPI.

@lbaillysalins you should be able to update to 0.24.0 via pip install -U km3io in a few minutes. If you are using Lyon CC, just reload the Python session after https://git.km3net.de/km3py/km3io/-/pipelines/23148 is finished

added enhancement label

It works all fine, thank you very much @vpestel and @tgal for fixing it so quickly :)