Dascore 0.2.0

[d-chambers]

Just jotting down a few todos/ideas before DASCore's 0.2 release. This is mainly a personal brain dump.

• Coord support for strings
• Spool group columns that get passed to merging etc.
• coord groupby object? Spool groupby?
• Spool.put for adding contents.
• Big spool refactor
• array API support; patch function dispatch for array backends.
• add option for full_coords in FiberIO.scan; that way when complicated merges are requested the spool can lazily load the coords it needs.
  -coord hash function; include on summaries.
• Clean up deprecation

[andreas-wuestefeld]

@d-chambers
May I suggest to actually move to a Version 1.0.0
I've heard comments that DAScore is still experimental, having such low version numbers :-)

And it definitely has reached maturity level 1.0 a long while ago

The change you describe here are worthy of version 2.0.0

[d-chambers]

May I suggest to actually move to a Version 1.0.0. I've heard comments that DAScore is still experimental, having such low version numbers :-) And it definitely has reached maturity level 1.0 a long while ago

Yes, not a bad suggestion. I guess I have inadvertently implemented 0-ver for DASCore, while it is actually quite mature, at least when compared to other OSS geophysics software. We are in good company though... SciPy was pre-1.0 for 16 years so our 3-5 years is not too bad 😉.

I will write up another discussion for developing a more realistic 1.0 road map.