Meta-issue: Metadata

[JaimeRZP]

Goal

Historically, Heracles operated purely on numpy arrays. Important quantities such as the bias or the spin were stored inside the np.array.dtype.metadata object.
As the code has developed we introduced the Result class that wraps the Heracles results in a more user friendly class.
However, in the process the metadata was left behind, sometimes still used, others forgotten.
The goal of this effort is to refine the metadata that we store and resurface it to the Result class.

Road map

• We want to make the bias a field of the result class as well but it is not clear how we will deal with the fact that not all results have a bias (PR: )
• We want to rework the metadata stored in the fields such as we don't need to pass the mapper to the transform funciton (PR: )

Associated issues

#286
#270
#265
#210
#201
You can help wikipedia by making this list longer.

[ntessore]

@JaimeRZP Thanks for taking on this herculean issue. I agree this is a larger issue with many symptoms, so I added the related issues as sub-issues of this one. Do you think we can open sub-issues also for the three items you identified in your roadmap?