Thank you for the feedback on the manual. Your suggestion to use the instrument in SUSTAIN helped me think about the next step: how we could take measurements in different places and make a fair comparison between them.
Based on the work I’ve done on the RM Young manual and your notes, I’ve put together the approach below. I’d start with a small set of locations at one height, work through a short recording in JADE, and then build a Python script around the actual files.
This is my first time putting together an experiment like this, so there are a few choices I’d want to work through with you before we run it.
These are my proposed next steps. I haven’t collected measurements for this plan yet.
02What I would build
A setup we can come back to.
A
A simple location plan and mounting setup
I’d choose a few positions along the tank with you and keep the instrument at the same height for the first pass. That would give us a starting point for comparing how the wind changes with distance from the front flap. We could add different heights once the basic routine is working.
I’d first check what mounting equipment we already have. Then I’d put together a sketch showing the positions, a consistent reference for the height, and which way the instrument faces. I’d want your input on where the support can go and how it might affect the airflow.
My question: Where would you like me to take the first few measurements? Should I start at one height before trying different heights?
First-pass layout / To discuss
Front flap→Nearer position→Middle position→Farther position
A sketch of the idea, not a scale drawing. Distances and height still need to be agreed.
B
A run sheet to keep each recording organized
I’d make a short sheet that connects each data file to its position, height, instrument orientation, tank settings, and any notes from the run. I’d also record the order we measured the locations in.
If we move one instrument between positions, I’d try to keep the conditions consistent and repeat a location to check for changes over time. I’d follow the lab’s procedure for stopping and repositioning the instrument.
My question: If I move the sensor between locations, how should I check that the wind conditions are still similar?
C
A JADE checklist I understand well enough to repeat
You mentioned that the three-dimensional wind recording is already configured. I’d like to go through a short saved file and make sure I understand the channels, units, timestamps, and any status flags. I’d also check which recorded direction corresponds to along the tank, across it, and up and down.
Before choosing a recording length, I’d check how often JADE saves readings and whether it averages or filters them. I’d use a pilot recording to discuss settling time and run length with you, then use the agreed settings consistently.
My question: Could we look at one JADE recording together so I can check that I understand what each column means?
03Python & graphs
Start with graphs we can actually use.
I’d build a small Python script that reads the JADE files, matches them to the run sheet, and checks for missing or flagged readings. I’d keep the raw files unchanged so we can always go back to them.
For the first version, these are the plots I’d focus on:
Wind over time
Look at each run before reducing it to an average. This would help us spot gaps, sudden changes, or periods we need to review.
Average vs. distance
Compare locations along the tank. I’d confirm whether we want the along-tank component, horizontal speed, or total 3D speed before calculating it.
Direction by location
Look for changes in airflow direction after checking the instrument’s orientation and the convention used for the angles.
Variation during a run
Show how much the readings move around their average. I’d add turbulence intensity once we’ve agreed on the component and calculation to use.
I’d bring back the first plots for feedback before building more around them. If we later measure at several heights, I could add a graph of wind speed versus height at each location.
04TCP/IP
Understand the connection first.
For the network side, I’d start by tracing how the readings get from the instrument to JADE and where TCP/IP would fit. I’d like to understand which device handles the network connection, what format the data arrive in, and how they get saved.
Once I understand that path, I’d put together a short connection diagram and, if appropriate, a small test that checks whether the expected records arrive correctly.
One thing I’m missing: Could you send the rest of the TCP/IP part of your email? My copy cuts off there. I’m still learning this part, so it would help to know which system to start with and who I should ask to walk me through it.
05Before I go further
A few things I’d like your input on.
Open a question for the detail I’d like to discuss.
What would you like me to start with?
Would it be most helpful if I start with a setup sketch, spend more time learning JADE, or try making a graph from an existing file?
What should I keep the same between measurements?
For the first test, which fan setting should I use, and should the water be still? I want to make sure I’m comparing the locations fairly.
Do we already have a way to mount the sensor?
Is there a stand or mount in the lab that I should look at? Could you show me where we can safely put it and how to move it between runs?
How long should I record at each spot?
Is there a recording length you normally start with? I’d also like to know how long to wait after changing a setting and whether I should record each spot more than once.
For my next check-in, I’d aim to bring a location sketch, a run sheet, and a short JADE file walkthrough. After your feedback, I’d use those to build the first version of the Python script.
Let me know if you’d rather I start with a different part. I’d like to get the first setup right and build from there.
Joseph
06Next steps
My first check-in.
These are the pieces I’d prepare next, with your input. The checklist is here to keep track as I work through them.
0 of 4 marked ready
Saved only in this browser. These ticks are personal notes, not shared experiment results.