kkappler

Id suggest for now that greater than 2^32 should get a warning. Most systems are 24 bit but there are 32 bit out there, so total number of available counts...

@kujaku11 : please create a folder under mth5_test_data/mth5_test_data/calibration_files/ and dump in there. Thanks

Or, a future version could be based on [pydantic](https://docs.pydantic.dev/latest/)

Prototype for this is working. Could benefit from #212

This functionality is coming along, however, more work is needed. - [ ] The `FCRunChunk` object should be moved to `mt_metadata`, as it is a descriptor of a chunk of...

This is more or less working now. However, there is an issue that has come to light after updating the metadata structures in the FC layers. The issue is that...

@kujaku11 Let's put this one on the backburner until after we have merged our branches into ```dev```

This is implemented on `features` and this issue can be closed once the initial features branch merges to master.

I put a table listing data that I have worked with in the past couple of months which maybe helpful as a template. [test_mth5_examples.csv](https://github.com/kujaku11/mth5/files/7197987/test_mth5_examples.csv) Note that when reading the table...

I have applied the following (uncommitted) workaround: in mth5/timeseries/run_ts.py I added at line 413: ``` if channel_ts.channel_metadata.component=="e1": channel_ts.channel_metadata.component="ex" if channel_ts.channel_metadata.component=="e2": channel_ts.channel_metadata.component="ey" if channel_ts.channel_metadata.component=="h1": channel_ts.channel_metadata.component="hx" if channel_ts.channel_metadata.component=="h2": channel_ts.channel_metadata.component="hy" if channel_ts.channel_metadata.component=="h3": channel_ts.channel_metadata.component="hz"...