Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

T program no longer writes velocities to .kel files #2

Open
dave290 opened this issue May 25, 2022 · 6 comments
Open

T program no longer writes velocities to .kel files #2

dave290 opened this issue May 25, 2022 · 6 comments

Comments

@dave290
Copy link

dave290 commented May 25, 2022

Hello! Up until recently, the T program would write velocities (instead of frequencies) to the .kel file, when the -V and -W flags were used. I updated the analyze package a few months ago and just noticed that instead of velocities, frequencies (in Hz) are written instead, even though the labels within the .kel file say 'velocity.' I did a git pull this morning and see the same issue.

For example, you should see it if you run T with the data files that are provided in the complimentary data set (18-11-01T*...18-11-02T*) using the command below:
T -B -L -200 -H +200 -V -W 600 *
and other related commands, like:
T -W 600 *

When the .kel file is written, the data lists frequencies instead of velocities (see example below):

N Velocity Intensity

(m/sec) (Kelvins)

0000 1419981933 -0.4236

Note that T does, in fact, plot the velocity range correctly.
I dove into the code, but it's not obvious to me what to modify.
Could you please take a look? Thank you!

@glangsto
Copy link
Owner

glangsto commented May 25, 2022 via email

@dave290
Copy link
Author

dave290 commented May 25, 2022 via email

@dave290
Copy link
Author

dave290 commented May 25, 2022

...Or, whichever is easier for you, in terms of which velocities are written to file.

@dave290
Copy link
Author

dave290 commented Jun 5, 2022

Hey Glen,

Just checking in about the velocity-writing issue with T.py
I have a student working on data analysis this summer and wanted to let her know when to update the analyze package.
No rush; if it's later, just let me know.

Thanks!
Dave

@dave290
Copy link
Author

dave290 commented Jun 12, 2022

Thank you so much for updating the code with the fix. Works just fine again!
Best,
Dave

@glangsto
Copy link
Owner

glangsto commented Jun 12, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants