Roadmap to v1.0

Here are the tasks and unresolved things for 1.0

• #39 (closed) best_reco(tracks, strategy) implementation. Together with @zaly and @mlincetto we talked about implementing such a function to create an entry point for the best reconstructed tracks. The strategy parameter should be mandatory with no default value, so that we avoid ambiguity in future versions. This means that the user needs to invoke the function with a specific strategy, like selected_tracks = best_reco(f.events.tracks, strategy="first") (simply selects the first track in each event).

• !24 (closed) Slicing consistency There is some refactoring on-going in the branch !22 (closed) which needs to be cleaned up and separated out in different branches. One of them will involve a new slicing implementation in offline.py which needs to be tested

• Detector file I/O (applying calibrations?)

added discussion label

changed the description

changed the description

changed the description

marked the checklist item !24 (closed) Slicing consistency as completed

marked the checklist item #39 (closed) best_reco(tracks, strategy) implementation. as completed

@tgal

Could you please elaborate the plan for Detector file I/O with km3io?

I found this https://km3py.pages.km3net.de/km3pipe/_modules/km3pipe/hardware.html#Detector and I was wondering if the plan is to somehow use what's implemented here?

thanks

Yes we should move this to km3io in my opinion. It's a bit difficult because the whole Calibration stuff is also in km3pipe, so either we move everything or nothing the other problem is that calibration stuff is tied to the database, so database functionality then (which is also some kind of an I/O) should be moved either

closed