-
Notifications
You must be signed in to change notification settings - Fork 3
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
DAC calibration #123
DAC calibration #123
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #123 +/- ##
=======================================
Coverage 93.96% 93.96%
=======================================
Files 12 12
Lines 729 729
=======================================
Hits 685 685
Misses 44 44
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The rst is not a bad idea, since we're rendering it as docs, and all our Sphinx is made of rst. So, it's one of the best solutions for this However, the idea is that you should always commit the source of your code, in such a way that you can still modify in the original way (even if it's a different person on a different machine, cloning from scratch). In general, notebooks are great, but what's the best way to include them is still something that I have to work out. And there could be multiple best solutions, according to the situation. |
Ok, scrape the rant above: in this case is not going to be included in the docs, so the plain notebook could be the solution. Otherwise, you could try Jupytext with Python. |
Makes sense to just use jupyters. At least for "examples" of this sort |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, let me submit the comments, since the file just changed :P
two samples) | ||
|
||
In this document we will present a way of calibrating these units from | ||
the values measured using a Spectrum Analyzer. The final objective is to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to have a Qibolab driver even for that :P
|
||
QICK (and therefore Qibosoq) uses arbitrary units to set the amplitudes | ||
of its pulses. It is not easy to directly connect a specific value of | ||
amplitude to a physical one in volt or dBm because this depends on two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about the meaning of expressing a tension in dBm
. That should be the attenuation, but on top of somehting - and usually that something is the DAC output, so you will need sooner or later a value in Volt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I confused dB
and dBm
. However, why you should measure a pulse in W? Are you assuming the output current to be fixed? Doesn't it also depend on the load?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dBm are the standard in this type of measurements, I think that's the case beacuse the load is always fixed at 50 Ohm
Unfortunately, GitHub gives nice rendering even for Notebooks diffs, but I can not comment on the lines. So all the review comments will be just on the file. |
|
||
QICK (and therefore Qibosoq) uses arbitrary units to set the amplitudes | ||
of its pulses. It is not easy to directly connect a specific value of | ||
amplitude to a physical one in volt or dBm because this depends on two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I confused dB
and dBm
. However, why you should measure a pulse in W? Are you assuming the output current to be fixed? Doesn't it also depend on the load?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will read it again, and in case provide further suggestions. But in general it seems good and useful.
Thanks @rodolfocarobene!
This PR adds a notebook (in rst format) that explain how to calibrate DACs in order to get a function that converts a frequency/amplitude/reconstuction-waveform to dBm (@marcogobbo).
I would like to add sooner or later also a notebook with the corresponding ADC calibration, but let's start from here.
Is there a better way of uploading a jupyter notebook, @alecandido? Maybe having this rst is worse than the notebook itself, but I was not sure what the best option was.
Checklist before merge: