Wip/simulated data acquirer with callback gradients#68
Open
domess wants to merge 55 commits into
Conversation
… without a voltage control component
…uts. It now works for any user-defined example.
…t__) instead of the function get_voltage_control_component()
… does not match the number of voltage parameters. In case no labels are provided, use default labels vg1, vg2, ...
…r is 0, i.e. the first defined sensor.
…h QCodes Parameters. Added Type checking to BasicParameter
…f values. This is done by adding wrapper class CallbackParameter
…ts-on-simulated-data-acquirer
…e Sensors" button actually computes the gate compensation and the fitted compensation matrix P_c is displayed in the annotation tab. This only works for simulated data, so far. Note that P_c is the unity matrix, since there is no P_c implemented in the QDarts simulator.
…ntral point plus/minus delta). Prepared for incorporating coordinate transformation into the simulated values.
…nted: a faster algorithm (align linearly) and a slower algorithm (sensor response is modelled as a sum of Gaussian basis functions).
…t GMM. The button does not work yet.
…ayed when pressing the button, and a warped image is shown. Everything works properly. Still to do: cleaning up.
…image_gradients()
- The normals are now pointing in the positive x- and y-direction (origin lower left)
… a nested dataclass in a file config.py.
…ressing the button Compute Transformation Matrix. This only works in case of the simulated data acquirer. So far this only works in the live data tab. Axes are not transformed.
…trix A_inv when pressing the button Calculate Slopes of Added Lines.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a new button "Compute Transformation Matrix":
Based on the current base image, the coordinates are changed, such that the transition lines become orthogonal to each other for newly acquired data (can only be seen in the Live View, or one has to press first the button "Import Live View" in the Annotation & Analysis tab). The Transformation Matrix (new -> original coordinates) is displayed.
If there are exactly two annotated lines, the transformation matrix and slopes are computed when pressing the button "Calculate Slopes of Added Lines". Otherwise, only slopes are computed.
All the parameters needed for the algorithms to compute the transformation matrix are in the config-file (folder video_mode/utils).
Note that Oswin's pull request #37 is added to the code.