Comments (4)
Hello,
You are indeed right that the first graph looks better. In fact, the right side of these two graphs are quite similar and the changes are the spikes from the left side that are higher on the second graph.
Regarding the green zones, they are in fact not calculated using a "constant" threshold. The goal is to take all kind of machines into account and guide the user to the speed ranges he can use based on his own graph. Here is how I calculate these zones:
- First, I calculate the mean and standard deviation of the entire signal. This is used to establish a baseline for what will be the "low energy zones".
- Then I compute a dynamic threshold (valid only for this signal) as the mean value minus 0.1 * standard deviation. This allows this threshold to depend on the signal's height, but also to account for a very noisy signal to avoid selecting small peaks. This 0.1 value was found experimentally on a large set of graphs to find something that works pretty well for everyone.
- The low energy zones are then identified on the graph by looking at the parts below this threshold.
- Finally, the low energy zones are also sorted by calculating their mean value and comparing it to the mean energy of the entire signal calculated at step 1. This comparaison is expressed as a percentage in the upper legend for each zone.
from klippain-shaketune.
Hello, I've fully reworked the vibration measurement macro and script so this issue is a bit outdated. Can you try the new tool?
If there's still some need, do not hesitate to reopen this issue :)
from klippain-shaketune.
I see it as follows:
First of all you need to calculate the total amount of energy in those vibrations.
I take it simply, may not be perfect but will serve the purpose.
Max value of peak and then take the percentage of that zone. In the top graph this is 1.8*10^7=18000000
26.54%=4777200 of whatever units is in the graph.
In the bottom graph there are 5 zones.
1st zone is already 3504000
2nd zone is 6660000
3rd zone is 7892000
4th and 5th zones are even bigger. When you add them up you get a far bigger amount of energy that goes into the vibration.
Apart from the fact you have only 1 zone in the first graph, the total energy is far far less as well so the top graph is way better I think.
Now I am in no way an expert in these graphs but I merely follow some logic when looking at the values displayed in the graphs and this conclusion is what I made out of it.
I am also interesting to see what others have to say about it, always up for learning something new.
from klippain-shaketune.
That's neat. Sounds you really thought it through to make it work in a large range of different printers which is great.
Somehow I think that having a somewhat less dynamically calculated threshold could improve the green zones. I'm not exactly sure how, but if I consider my own two graphs I can't help but think that the first graph should be mostly green, at least up to 350mm/s. But I understand if someone runs this on a very noisy printer and even the lowest is above 4.0 1e7, you need some way to mark the best zones to stay in. In that case your algorithm works great.
Perhaps here's an idea. As with input shaper profiles, there is often a choice for performance (ie, ZV), and one for quality (ie, MZV). Maybe you could allow for a similar choice in determining the green zones. In my case, if I would choose quality, the green zone threshold would be lower resulting in potentially less green zones and lower max print speeds. But if I choose performance, it would allow for a higher threshold and larger (or more) green zones.
Give it a thought!
from klippain-shaketune.
Related Issues (20)
- asxl chip error running vibrations measurement HOT 4
- AXES_SHAPER_CALIBRATION results in a broken image in the results folder HOT 1
- Are the tests supposed to be done in a certain location on the XY?
- Capitilization of recommendations change, documentation change request. HOT 1
- Diffrent Results between Klippers Shaper Calibration and Klippain on X Axis HOT 2
- Error after running belt or input shaper calibration HOT 2
- vibrations - Error while generating the graphs HOT 1
- S&T will not create the graph HOT 3
- S&T new version not generating Graph after running. HOT 5
- AXES_MAP_CALIBRATION not outputing any information HOT 3
- Measure Fan Vibration HOT 4
- AXES_SHAPER_CALIBRATION doesn't generate graph HOT 3
- accel_per_hz support HOT 1
- Добавить в описание по установке пункт: "Обязательно добавить секцию [resonance_tester] в printer.cfg".
- Backup and Uninstall HOT 2
- Support hybrid_corexy machines HOT 4
- Error running command after update to v3 HOT 3
- Not showing *.png on interface HOT 3
- run COMPARE_BELTS_RESPONSES and AXES_MAP_CALIBRATION get error HOT 1
- AXES_MAP_CALIBRATION: 'AxesMapFinder' object has no attribute 'create_graph' HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from klippain-shaketune.