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

[Sleep] Channel amplitude max limited #31

Closed
skjerns opened this issue Oct 19, 2018 · 10 comments
Closed

[Sleep] Channel amplitude max limited #31

skjerns opened this issue Oct 19, 2018 · 10 comments
Labels

Comments

@skjerns
Copy link
Contributor

skjerns commented Oct 19, 2018

Currently, the maximum channel amplitude is set to the maximum of the signal. However, in some cases (such as large monitors with clipped signals) it can be preferable to set the maximum channel amplitude (= the scaling) to a higher value (that means, decrease the displayed channel amplitudes).

Suggestion: Remove the upper limit of the maximum amplitude scaling.

I tried to look in the source where I can change this (i.e. _PanAllAmpMax), however, I could not find where the maximum value restriction is set (no call to _PanAllAmpMax.setMaximum anywhere).

@skjerns skjerns changed the title [Sleep] Channel amplitude min/max [Sleep] Channel amplitude max limited Oct 19, 2018
@EtienneCmb EtienneCmb added the bug label Oct 19, 2018
@EtienneCmb
Copy link
Owner

Why would you like to have a smaller signal on the screen?

@EtienneCmb EtienneCmb added question and removed bug labels Oct 19, 2018
@skjerns
Copy link
Contributor Author

skjerns commented Oct 19, 2018

Some of my recordings have quite low recording range: this makes low amplitudes appear as massive, if they are not not rescaled. This becomes even more a problem if the window is maximized on a large scree0n (=height being the factor).

Example:
capture
For me, the third display is far better and quicker to interpret and spot the spindles. (disregard the uV scale at the left, it is not correct)

Most GUIs I worked with were allowing to rescale the signal as big/small as required. Would that be an idea here as well?

@EtienneCmb
Copy link
Owner

I'm not sure to understand your point, from the GUI you can rescale each channel independently. Are talking about the default behavior of the GUI i.e without further configurations?

@skjerns
Copy link
Contributor Author

skjerns commented Oct 19, 2018

While I can rescale each channel independently, I can't rescale it smaller than a specific factor. Currently the rescaling is limited by the ['max'] of the channel. In my case, the physical ['max'] is denoted as 40.25 (second line). This means I can't set the signal 'smaller' than the middle line in the picture above (maximum amplitde is 40.25). I had to change some parameters in the source to allow a scaling to a maximum amplitude of 90 as in the third signal. Does this make sense? It might be a bit hard to understand what I mean, indeed.

(btw the lines above are 3x the same channel, just with different scaling)

@EtienneCmb
Copy link
Owner

Hi @skjerns , sorry for the delay. I think I finally got your point. It's true that the min and max of the GUI elements are defined using the min and max of the data (see this function). But we could allow the user to used values under the min or over the max. We just need to find a range.

@skjerns
Copy link
Contributor Author

skjerns commented Dec 7, 2018

Why not leave it entirely up to the user, but set a reasonable standard value?
As the user will see immediate feedback on his actions, it's their responsibility to scale it to infinity.

@EtienneCmb
Copy link
Owner

At least we could set 10. * min() and 10. * max() this should provide a sufficient range

@skjerns
Copy link
Contributor Author

skjerns commented Dec 7, 2018

sounds reasonable!

@EtienneCmb
Copy link
Owner

Hello @skjerns ,

Sorry for the delay. I recently push a modification (cb36e8a) to limit channel amplitudes to (10 * min, 10 * max). This should fix your issue?

@skjerns
Copy link
Contributor Author

skjerns commented Jan 10, 2019

it does :) thanks a lot!

@skjerns skjerns closed this as completed Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants