Vectrino II data description

Up to Velocimeters - single point

Vectrino II data description

Posted by Tim Calappi at November 04. 2011

Hi,

I collected some data with the Vectrino II and exported it to Matlab. I'm trying to figure out some of the variables. Most are easy to figure out but I was wondering if there is a document with a complete description? Specifically I'm trying to figure out Data.BottomCheck_Range. I found the entry in the Units structure but not the comments structure.

I can't relate the size of BottomCheck_Range( 1 row 85 columns) back to my flume geometry or configuration file. The values in this variable range from 0.03 to 0.2. The only thing in my setup that's in this range are velocities but the Units structure has this variable in meters.

Thanks,

Tim

Re: Vectrino II data description

Posted by P.J. Rusello at November 04. 2011

I don't think we have a document describing each of the fields. I'll check with someone on that, but largely the variable names are meant to be descriptive enough.

Data.BottomCheck_Range however follows the same convention as Data.Profiles_Range, providing positions of the cells used in the bottom detection algorithm. So you could plot an individual bottom detection ping as

plot( Data.BottomCheck_CenterBeamAmplitude, Data.BottomCheck_Range )

Hope that helps.

Re: Vectrino II data description

Posted by Tim Calappi at November 10. 2011

Thanks P.J. Just to make sure I understand....The depth in my flume is 8 cm and I used most of the default configurations for most of the stuff that is new to the Vectrino II.

 

The bottom check configuration range is between 30 and 200 mm. So the Vectrino started looking for the bottom 30mm away from the transmitter and stopped looking 200mm away from the transmitter. Given the depth in my flume, I could have changed the max depth to 80mm if it was a fixed bed but 90 or 100mm and would be better for a slightly mobile bed. I assume there is no harm looking out 200mm in my case?

Re: Vectrino II data description

Posted by P.J. Rusello at November 10. 2011
Probably no problem looking out to 200 mm. Just to be sure though take a look at the reported bottom distance and make sure it's reasonable and an echo isn't being identified as the bottom peak. You can see the realtime fitting process by looking at the "Center Beam" tab during data collection. Personally, if you know the bottom can't be farther than 80mm, I would set the maximum range a bit further than that (say 85-90 mm) just to make post processing easier. There won't be any really outlandish outliers (which are admittedly easy to detect) if you do this.
Powered by Ploneboard
Document Actions
Log in


Forgot your password?
New user?