write here



yep

so i fixed the code, i just need to upload this
 
to the araduino

are you sure?  it didn't take long.

yeah it was a really silly thing i left in

are you sure there aren't any other silly things?

yes, this was very silly of me

arduino is plugged in

only thing that moves the turntable is the "forward()" function, i left one in on accident.

all good now

so do we have some idea of what the turntable was doing over the past two days?

so it was logging the wind dir. input and the output turntable position

this would all be relative to how you positioned it. like instead of 1500 steps relative to zero, 
it'd be with wherever you positioned the turntable(with that as the zero)

I checked on it at least once yesterday and it didn't appear to have moved...

when did you start logging the winds?  That's when this started, right?

8/19 9:49 am

it seems it was probably rotating to the read position and indexing back to zero the whole time

no tangles?

it doens't appear to have damaged anything. luckily

when you say probably rotating to the read position, what does that mean?

you think it kept the starting position as opposed to making that the new zero?

no, the zero would be wherever you positioned it at the start. and it would rotate to a read position
(like +1500 step), then back to where it started. The zero shouldn't have changed.

those seem like two contradictory statements.  the zero changed when I repositioned it and restarted it.

It changes whenever you restart the code. sorry if not clear.

When you start up the code, it assumes that is the zero point.

this morning it was pointing close to where I had left it last night.  and the winds had changed from sw to north westerly.  So I'm trying to figure out what that means.


one sec. the logs say the wind direction did change. around 60-80 degrees

yes, the winds did change. from sw to nw
the  bturntable should have moved to those positions as well after they changed.

but the turntable was positioned to the sw yesterday when I checked on it and sw today when I checked on it.

I might head up. It shouldnt have done that, althoug hthe code changed so it may not have the issue now.
Im not sure why that is. It would have done that had it not been rotating

I don't know...

when I repositioned it this morning, I pointed it pretty close to north (since that's where the wind was coming), so maybe the data today is ok...

yesterday's data is suspect.

Assuming it was rotating this morning as well, was it still pointed north at the end?

at the end?  You mean just now?
yes
yes
well nw I guess
anyway, the same place I had positioned it

alright. well it isnt moving now, and the log gives a sense of when the fssp did move(last night)

yeah the data last night was definitely not good.  but I figured that was just because the wind direction changed (and I had it pointed in what I thought was a constant direction)

now I'll have to check the data during the day yesterday and see if the positiong (from your log files) corresponds to any changes in the data

the fssp, if moving, wouldnt be pointed towards your zero long enough for meaningful data in my opinion
but yeah that would be a good check. let me know if i can do anything on the data log side of things.

yes all the data might be crap

sorry

if it was zeroed towards north and moving back and forth then thered be actual data, sorry about missing that function

should I head up?

I'm reasonably satisfied that it's not going to rotate anymore.  was just sitting up there waiting to see if it would

this will be a good test for how closely we need to be to the actual wind direction (maybe) - so we'll get something out of it.  perfect kind of test for a pilot study

I'm not sure if you should head up.  like you said, it was just a silly thing, not something we still need to figure out

I can make a document with the times it moved and to where for hte past day or so. it stays at zero for 
~3-4 seconds in between position changes. should clariy some data (?)

I can get that from the log file, yes?

I'lyle jup, might just be a little hard to read. the last column is current position. check when it changes.

sorry for writing over you.  I'll just plot the current position vs time and compare to the drop size distribution.

the time is one question.  They are not necessarily on the same clock....

FSSP uses laptop clock or internal? because gobetwino uses laptop clock

ok I think that's all I need to know.  I'll check on the FSSP, exactly.

yep might be the same clock.  I know it's UTC in the datafiles, but it might have a battery...?  not sure

ok I'm going to close this and play around iwth the clock

ok! let me know if you need anything. ill make some plots

ok
yeah it would be good to write something up from your perspective.  I'll do the same.
ok