Code Monkey home page Code Monkey logo

Comments (4)

matthiasbirkich avatar matthiasbirkich commented on September 3, 2024

output_test_20210228.xlsx
The reference is FALSE and the molinity will not be calculated.
This was the failing "test_dataset_io.py" script. What a pity. I am sure, it is running in your environment...
best. M

from calkulate.

matthiasbirkich avatar matthiasbirkich commented on September 3, 2024

Dear developers,
when we are using strictly *.csv-file formate, than no error occurs during calculation. :-).
But the solved alkalinity values are still NaN. :-(.
Are you so polite to explain, how I can calculate a single file with given molinity for DIC and Alkalinity to a Python analphabet?
It would be really great for us to implement your Calkulate package in our routine analysis.
With PyCO2 we don't have any problems and with vindta_reCALk package we are also able to recalculate our old VINDTA data.
The goal of our team is:
Take the Dickson standard (which is NOT available at the moment) as a control and calibrate with Na2CO3-standard as it is described in the PICES 2007 document and the Vindta manual as well. Using the Dickson CRM as CONTROL is a consistent procedure in chemical analytics in our opinion. The QUASIMEME round AQ15 will go for Alkalinity and DIC.
We want to establish a possibility to be independent from Andrews CRMs, when they are not available.
For this we need to adjust the molinity according to the zero values of sulphate and fluoride, which we don't want to add to our pure Na2CO3-standard. NaCl we have to add, because of the liquid junction potential of the electrode. This circumstance we can only control with the more flexible Calkulate/PyCO2-package. What do you think about this issue? We will be glad to hear from you.

Best regards and take care
Matthias

from calkulate.

d-sandborn avatar d-sandborn commented on September 3, 2024

I have been able to replicate this issue. Running the "Basic Use" code for the "titration_table.csv" metadatafile provided at https://calkulate.readthedocs.io/en/latest/ gives the following output in Spyder 4.1 running Python 3.7 and Calkulate 23.0.1:

Calkulate: calibrating titrant_molinity...
Calkulate: ERROR calibrating 'seawater-CRM-144.dat'!
Calkulate: ERROR calibrating 'filename-does-not-exist.dat'!
Calkulate: ERROR calibrating 'seawater-CRM-144-function.dat'!
Calkulate: ERROR calibrating 'seawater-CRM-144-method.dat'!
Calkulate: ERROR calibrating 'Dickson-1981-pH-no_phosphate.dat'!
Calkulate: ERROR calibrating 'Dickson-1981-pH-with_phosphate.dat'!
Calkulate: calibration complete!
Calkulate: solving alkalinity...
Calkulate: solving complete!

I saved the resulting dataframe and attached it below.
data.txt

I've also been wrestling with similar problems over the last week or two. I have not yet found a repeatable way to modify the titration metadata table to calculate alkalinity successfully. I'll keep working on this.

EDIT
A few more notes. Line numbers refer to the rows of titration_table, beginning at 1 (not 0).

  • Line 4 is calibrated and solved iff current working directory is set to the folder containing ~tests\data.

  • Lines 1, 3, 4 are calibrated and solved when "" and temperature_override is set to 25, but lines 5, 6 aren't.

  • "filename-does-not-exist.dat" is never solved nor calibrated.

  • Even if all metadata columns after the file_name are replaced by those of the successfully solved-and-calculated line 4, only line 1, 3, 4 are successfully calibrated and solved.

This may be a titrant calibration error, but it's still unclear where the error is occurring. I can't imagine why the Dickson-1981 files refuse to calibrate or solve.

from calkulate.

matthiasbirkich avatar matthiasbirkich commented on September 3, 2024

Dear developers,
now I am able to work with the program. I studied the "test_dataset_manual.py" and understood:
I haven't put a value to "alkalinity_certified" for the samples, which I wanted to calculate for alkalinity.
In all other programs (seacarb, Dicksons Gran-plot, others) it is not necessary.
Sorry, that I put that issue into this channel. I would like to apologize for this behavior.
One question:
Is it planned to go for the calculation of DIC as well, like the publication of Dickson D81 with the itterative method?
That would be really great.
best regards
Matthias

from calkulate.

Related Issues (11)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.