Skip to content

Releases: laccore/data-aggregator-and-renamer

Data Aggregator v1.2.1

15 Nov 23:09
Compare
Choose a tag to compare

Changes to MSCL-XYZ processing:

  • Data Directory Naming Convention defaults to "-part"
  • Drop "Depth in Core" column
  • Do not drop "Munsell Colour" column

Data Aggregator v1.2.0

28 Jul 19:57
Compare
Choose a tag to compare

Changes:

  • Include first row of MSCL data in aggregated file
  • Dropdown to select appropriate data directory naming convention (-p, -part, _p, _part) for MSCL and XYZ data

Data Aggregator and Renamer - now with QOL improvements

02 Mar 21:14
Compare
Choose a tag to compare

New additions and bug fixes:

  • Optionally filter Magnetic Susceptibility values below -50 from the XYZ dataset (the MS sensor records incorrect/not real values around -300).
  • Ignore additional columns in the core list file when renaming. This commonly showed as empty columns that Excel would still include
  • Strip whitespace from the core list file so numbers can be properly cast as integers
  • Guess at file encoding when opening files and export in the preferred encoding of the system, both of which should result in less formatting problems reading and opening processed files across different systems

Data Aggregator with CoreID Renaming

03 Jul 20:29
8c11703
Compare
Choose a tag to compare

And some bug fixes and other changes:

  • Export correct units for MS on XYZ aggregation
  • Change column order or corelist file to be coreID,section number

Data Aggregator and CoreID Renaming

30 May 20:59
Compare
Choose a tag to compare
Pre-release

This release combines the Data Aggregator functionality with the ability to assign CoreIDs to the aggregated data based on a corelist.csv file.

Data Aggregator - it mostly works!

29 May 19:20
Compare
Choose a tag to compare
Pre-release

This first release should work for all datasets we see at the CSDCO on a regular basis.

There are some major limitations, all around the XYZ Aggregator. It will probably need a fairly significant rewrite of parts of it, which is on the list but not done yet. Currently it will only correctly work if and only if the input files have the exact columns it expects to see. It's very fragile (hence why I couldn't comfortably call this v1.0.0). But if we export correctly from the Geotek software, it works fine and will save so much time.