no more unflagged column

• i removed the unflagged column at all.
• now History() takes a mandatory index at creation an nothing more.
• to create a History from data (hist-df, mask-df, and meta list) one can call createHistory(..)
• History.max() still return UNFLAGGED, even for empty Histories, which is possible now because of the inital passed index

only this commit - !285 (73708889) is relevant, the rest comes from historymeta (!284 (merged) )

i dont know where the translator rely on the UNFLAGGED-column, but this we need to adjust, i guess..

i also dont know if we want to go down the line, but i would say we have to decide which way we want to go:

• a) without UNFLAGGED-column with quite simple history-creation, (mandatory index to __init__)
• b) with UNFLAGGED-column, more complex History creation (hist, mask, meta are needed), except passing no args at all (empty History)

requested review from @schaefed

added cleanup/refactoring internal architecture + 1 deleted label

mentioned in merge request !284 (merged)

changed the description

assigned to @palmb

Now, that I arranged myself, with the initial column, you wan't to steal from me again ?

Just kidding, if this works out, I am in favor of the change. But TBH, I currently don't really oversee all the moving parts, that might be affected by this.

added 1 commit

• 118c50b1 - simplified copy

Compare with previous version

added 1 commit

• 9190ef91 - fixed docu, and minor leftovers

Compare with previous version

so you approve ? then i merge it back to !284 (merged)

resolved all threads

resolved all threads

approved this merge request

changed title from WIP no more unflagged column to no more unflagged column

merged in !284 (merged)

closed