calibrate_pitot: cal_time_range is not being used

[dcherian]

Hey it looks like cal_time_range is not used anymore? But that variable still exists. I'm getting merge conflicts so wondering why...

[dcherian]

Similarly, looks like the default pitot speed estimate is 30s instead of 10min? Is this intentional?

[jbecherer]

your are right cal_range is not used anymore... there is no reason to keep it I guess...

the 30 sec, was me beeing lacy and not wanting to change it anytime I pull a fresh version :)
because for my deployments it is the best, but we can change it back... no objections.

[dcherian]

the 30 sec, was me beeing lacy and not wanting to change it anytime I pull a fresh version :)

I've been dealing with this by having a branch that's particular to each "experiment" for experiment-specific default settings. And then I have instrument specific branches.

E.g. "master -> rama -> rama13-526" with each branch building on top of each other. It makes things complicated but it's relatively easy to ensure that all RAMA chipods have the same set of defaults.

[jbecherer]

That's smart..
I kind of solved it by not doing the processing locally, but with my mooring builder routines and the
database. But I am not super consistent.