Git Product home page Git Product logo

Comments (4)

0xCoto avatar 0xCoto commented on May 24, 2024

The waterfall is structured like this:
image

(where Z used to express the waterfall, Zmean -> avg_spectrum (averaged (uncalibrated) spectrum) and W-> power (power vs time))

The waterfall includes all information post-FFT: the relative power as a function of frequency and as a function of time. As the observation is running (data acquisition), GNU Radio appends a new row at the bottom. So, each row represents an "instantaneous-ish" spectrum.

The power unit is arbitrary ("relative power" or "counts") and depends on the SDR, gain etc. dB can be enabled and automatically rescaled with dB=True, but this should not be confused with dBm (decibels relative to 1 mW) which is an absolute scale. S/N only pops up when the spectrum is calibrated and makes sense to use the "noise" segment of the spectrum (the flat region, i.e. when passband shape has been corrected to take the standard deviation for the noise level, with e.g. the HI signal masked).

I believe you won't need to pay too much attention to the structure of waterfall for VLSR corrections though (unless you're asking out of general curiosity). I think the only thing that has to be adjusted is the secondary X-axis of the averaged spectrum and (inherently) the calibrated spectrum, indicating velocity.

from virgo.

kevinawilson avatar kevinawilson commented on May 24, 2024

In virgo.py line 544, you convert epoch time to mjd by dividing the epoch time by 86400, which gives the number of days. You then add 40587. What does this number represent? It seems to add about 111 years to the date.

I've been able to account for VLSR in the plot. Right now I'm trying to decide how to store galactic lat/long and observer location, as both of these are needed to convert to VLSR. I will probably save them in the header files so they can be retrieved later.

from virgo.

0xCoto avatar 0xCoto commented on May 24, 2024

I'd have to search where exactly I got these numbers from, but I just checked and the calculation is correct. E.g.
python -c "import time;print(time.time())" returns 1625836986.22, and plugging this number here gives 07-09-2021, so it looks correct.

from virgo.

0xCoto avatar 0xCoto commented on May 24, 2024

Kinda relevant: http://www.sp.ph.ic.ac.uk/csc-web/MJD/MJDtime.htm

Note that MJD for 1 Jan 1970 is 40587 (used for the Unix start epoch) and MJD for 1 Jan 2000 is 51544 (used by QSAS internally).

from virgo.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.