Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import ".deg" immersion files from Migrate Tech Intigeo tags #7

Open
HendrikSchultz opened this issue Dec 27, 2016 · 2 comments
Open

Comments

@HendrikSchultz
Copy link

HendrikSchultz commented Dec 27, 2016

Hi there and a belated merry Christmas,

I was just looking into importing ".deg" files (immersion count data as provided by Migrate Tech Intigeo loggers) into BAStag and was delighted to see that a function ("readMTdeg") has recently been added. However, I was confused when reading the description of the function, which states "Read Temperature data from a Migrate Technologies tag", which basically resembles the description of "readMTsst" which serves to importing ".SST" files (which contain temperature and conductivity data). Importantly, ".deg" files (as provided by my Intigeo C250 tags) contain immersion count data only and no temperature/conductivity data. When executing "readMTdeg" I get:

Error in scan(file = file, what = what, sep = sep, quote = quote, dec = dec, :
line 1 did not have 6 elements

These six elements seem to be referring to the six elements found in the readMTsst function. I am therefore wondering whether the wrong parameters/column names may have accidentally slipped into the new "readMTdeg" function?

Thank you very much in advance for your comments.

With all the best wishes,

Hendrik

@J-Cleeland
Copy link

I also have this problem. See last issue raised. Attached is example .tem file converted to .txt for github approval.
GREPE_7A05309.txt

@J-Cleeland
Copy link

Hey @SWotherspoon and @mdsumner
Working with Paige (@Fregetta) on some GLS data and just a reminder that the readMTdeg doesn't quite fit the new Intigeo structure. Essentially there's no mean SST. Easy fix, but confusing for new folks.
Cheers,
Jaimie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants