×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

New KStars/Ekos Module: Analyze

  • Posts: 1208
  • Thank you received: 559
Ferrante,

Both of these very reasonable comments are more "UI features/bugs" than software issues.


<code>Disclaimer--I tried to document the Analyze interface in the KStars handbook and the "not too useful for Analyze at this point" Help button
points to that, but unfortunately, the online KStars Handbook has not been updated since before Analyze was pushed
due to some server issue.</code>
<strong>Temperature</strong>: There are many possible plots in Analyze, and many of them have different scales & offsets on their Y-axis.
The displayed y-axis refers to those that typically range in the single digits, like RA & DEC errors, RMS error, etc.
Temperature has its own scale, not displayed, and to get its value you look at the temperature box.
You can see the shape of the curve from the graph display, but not the actual value.
Same is true for "number of stars", "median sample value", ...
I could have come up with some complicated interface where you click on a feature whose y-axis should be added to the plot, but
I kept it simple for now and only show the one y-axis for RA/DEC/RMS/.... Happy to consider suggestions for other possible UIs.
Hopefully things will be more clear once the documentation goes online.

<strong>Details</strong>: You populate the details window and graph by clicking on a segment in the timeline. Then it displays details about that segment.
Try this for capture and focus timeline segments in particular.

BTW, thought not complete, there is some doc for Analyze on the first post in this thread.
Hy
The following user(s) said Thank You: Ferrante Enriques
Last edit: 3 years 3 months ago by Hy Murveit.
3 years 3 months ago #63634

Please Log in or Create an account to join the conversation.

  • Posts: 249
  • Thank you received: 62
thanks Hy for clarifying the features of this module and I will refer to the documentation in the future.

I used Analyze on a set of images taken last night and it helped a lot to choose which were good or not before downloading from the observatory.
To me it would also be useful if images that don't match some criteria (e.g. HFR>1.5, Eccentricity>0.6) could be discarded /deleted before saving.

Ferrante
3 years 3 months ago #63663

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic New KStars/Ekos Module: Analyze

Hello Hy, I have been using the Analyze tab a good bit lately, and find it helpful. I did find a couple things to report.

First, when I click on a "focus" segment or an captured image segment in the top section, I get these logs:
[2020-12-03T22:48:40.694 CST WARN ][                       default] - QString::arg: Argument missing: <tr><td style="color:yellow">HFR</td><td colspan="2">1.80</td></tr>, 
[2020-12-03T22:48:40.695 CST WARN ][                       default] - QString::arg: Argument missing: <tr><td style="color:yellow">Iterations</td><td colspan="2">18</td></tr>, 
[2020-12-03T22:48:40.695 CST WARN ][                       default] - QString::arg: Argument missing: <tr><td style="color:yellow">Filter</td><td colspan="2">Red</td></tr>, 
[2020-12-03T22:48:40.695 CST WARN ][                       default] - QString::arg: Argument missing: <tr><td style="color:yellow">Temperature</td><td colspan="2">6.0</td></tr>, 

Second, when I click on a focus segment in the top section, the details are vertical with 1 letter width (see attached image).




Thanks
Jim
Last edit: 3 years 3 months ago by Jim. Reason: attachment did not work
3 years 3 months ago #63840
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1208
  • Thank you received: 559
Thanks Jim. Not really sure what's going on there (clearly it works for me and some others). I wonder if it is a locale issue.
Can you say what your locale is? Can you test in other locales and see if it works? (Sorry, I'm new to this and don't really
know how to test with different locales). Would be happy to try and fix it if we knew more.

Hy
3 years 3 months ago #63868

Please Log in or Create an account to join the conversation.

  • Posts: 300
  • Thank you received: 57
Hy, Thank you very much for this very helpful module.

Would you consider turning off the guide panel if there's no guider set up, and then expanding gate vertical scale of the top two panels to fill the window?

I'm imaging unguided and my most important metric is eccentricity. There's so little vertical scale between 0 and 1 on the Statistics panel that it's hard to see what's going on.

Thanks again,
Scott
3 years 3 months ago #63899

Please Log in or Create an account to join the conversation.

  • Posts: 1208
  • Thank you received: 559
Scott,

I'm definitely struggling with how to plot all the different possible graphs there.
I'm not sure what you mean. When you say "turning off the guide panel", do you mean the bottom two displays (labelled Details)?

In any event, as a work around, until we figure something out (keep the suggestions coming), did you know that
you can put your mouse over a spot on the graph (e.g. right on some eccentricity value) and use the scroll where to zoom in to that spot.
You can then move your mouse over to the left to the y-axis, and drag the y-axis up and down.
If you use this technique, and turn off most other things, you can get a graph of eccentricity.
Here's a screenshot of me doing that.



I also want to warn you, that if you have quick HFR turned on, eccentricity is just calculated from the middle 25% of the image.
You can of course turn that off, but it may be computationally expensive on, e.g. a Raspberry Pi.

Hy
3 years 3 months ago #63901
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 300
  • Thank you received: 57
Hy, Thank you very much for reminding me that it's best to configure the graphs to emphasize what I need (eccentricity)!

That being said, what is the point of those two bottom panels marked "Details" if there's no guider? Seems like a lot of screen space for two blank panels.

For that matter, the Guide, Mount, and Capture rows of tick boxes could be collapsed under a pull-down or moved to a Settings panel to allow more space for Statistics.

The guide data is important, and it's certainly great to see it here in the context of the rest of an imaging session, but it would be excellent to toggle it off if there's no guider present at all.

Thanks again,
Scott
3 years 3 months ago #63913

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109

Replied by Jim on topic New KStars/Ekos Module: Analyze


Interestingly, other sections display correctly, it is only the focus details, as if it were trying to print into a narrow column in that field. I am using Qt 5.15-1 if that helps. I don't know much about LOCALES either, and have not changed them from the default system install, but will look into it.

Jim
3 years 3 months ago #63920

Please Log in or Create an account to join the conversation.

  • Posts: 1208
  • Thank you received: 559
Scott. That's something to think about.

FWIW,
  • The details graph on the right side also gives you an autofocus graph if you click the timeline section for an autofocus, and the left text section gives you information on any timeline section you click.
  • I use the numbers coming from the checkbox section more than I use the graphs. E.g. I'll click on the graph section to find a time and look at various numbers. You can even pan around in the graph and the numbers should update with your mouse.
I have no doubt this can be improved and your idea on hiding sections is interesting.
It may also be possible to pop-out a graph of interest.

Food for thought.
Hy
3 years 3 months ago #63941

Please Log in or Create an account to join the conversation.

  • Posts: 300
  • Thank you received: 57
Hy, I misunderstood the layout of these panels. Sorry about that -- I need to RTFM! Sure enough, great the way it is. -- Scott
3 years 3 months ago #63952

Please Log in or Create an account to join the conversation.

  • Posts: 37
  • Thank you received: 5
Weather has not been compliant. Had only a few days to try it.
But Man!!! Thank you so much, your module is so nice!
I Love absolutely everything about it, what a sweet addition to ekos.

--edit: in a way bad weather was perfect to test your module, as I could see drops in guiding SNR curves, assess quality of my gathering and evaluate situation....
The following user(s) said Thank You: Hy Murveit
Last edit: 3 years 1 month ago by Palmito.
3 years 1 month ago #66706

Please Log in or Create an account to join the conversation.

  • Posts: 163
  • Thank you received: 26
Just a quick note about the analyze tab:

-first of all- I use it a lot, it's an excellent overview and it really helps to better understand the overall session.

In the scheduler, I plan a few targets. The images from them can be opened by double clicking on the 'image trace' in the analyze tab.
But only for the first target.
When clicking the image trace for the next target, a popup shows noticing the image can't be found.
Can this be 'fixed'?

I use other names for my filters, so hereby I'm adding more names for the same filter in your code (see below).
I put it in <strong>bold</strong> font what I added. Feel free to add what you like (or nothing) :)

Cheers!bool filterStripeBrush(const QString &filter, QBrush *brush)
{
if (!filter.compare("red", Qt::CaseInsensitive) ||
!filter.compare("r", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::red, Qt::SolidPattern);
return true;
}
else if (!filter.compare("green", Qt::CaseInsensitive) ||
!filter.compare("g", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::green, Qt::SolidPattern);
return true;
}
else if (!filter.compare("blue", Qt::CaseInsensitive) ||
!filter.compare("b", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::blue, Qt::SolidPattern);
return true;
}
else if (!filter.compare("ha", Qt::CaseInsensitive) ||
!filter.compare("h", Qt::CaseInsensitive) ||
<strong>!filter.compare("h-a", Qt::CaseInsensitive) ||
!filter.compare("h_a", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("h-alpha", Qt::CaseInsensitive) ||
!filter.compare("hydrogen", Qt::CaseInsensitive) ||
!filter.compare("hydrogen_alpha", Qt::CaseInsensitive) ||
!filter.compare("hydrogen-alpha", Qt::CaseInsensitive) ||</strong>
!filter.compare("h_alpha", Qt::CaseInsensitive) ||
!filter.compare("halpha", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::darkRed, Qt::SolidPattern);
return true;
}
else if (!filter.compare("oiii", Qt::CaseInsensitive) ||
<strong>!filter.compare("oxygen", Qt::CaseInsensitive) ||
!filter.compare("oxygen_3", Qt::CaseInsensitive) ||
!filter.compare("oxygen-3", Qt::CaseInsensitive) ||
!filter.compare("oxygen_iii", Qt::CaseInsensitive) ||
!filter.compare("oxygen-iii", Qt::CaseInsensitive) ||
!filter.compare("o_iii", Qt::CaseInsensitive) ||
!filter.compare("o-iii", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("o_3", Qt::CaseInsensitive) ||
!filter.compare("o-3", Qt::CaseInsensitive) ||</strong>
!filter.compare("o3", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::cyan, Qt::SolidPattern);
return true;
}
else if (!filter.compare("sii", Qt::CaseInsensitive) ||
<strong>!filter.compare("sulphur", Qt::CaseInsensitive) ||
!filter.compare("sulphur_2", Qt::CaseInsensitive) ||
!filter.compare("sulphur-2", Qt::CaseInsensitive) ||
!filter.compare("sulphur_ii", Qt::CaseInsensitive) ||
!filter.compare("sulphur-ii", Qt::CaseInsensitive) ||
!filter.compare("s_ii", Qt::CaseInsensitive) ||
!filter.compare("s-ii", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("s_2", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("s-2", Qt::CaseInsensitive) ||</strong>
!filter.compare("s2", Qt::CaseInsensitive))
{
// Pink.
*brush = QBrush(QColor(255, 182, 193), Qt::SolidPattern);
return true;
}
else if (!filter.compare("lpr", Qt::CaseInsensitive) ||
!filter.compare("L", Qt::CaseInsensitive) ||
<strong>!filter.compare("UV-IR cut", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("UV-IR", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("white", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("monochrome", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("broadband", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("clear", Qt::CaseInsensitive) ||</strong>
<strong>!filter.compare("focus", Qt::CaseInsensitive) ||</strong>
!filter.compare("luminance", Qt::CaseInsensitive) ||
!filter.compare("lum", Qt::CaseInsensitive) ||
!filter.compare("lps", Qt::CaseInsensitive) ||
!filter.compare("cls", Qt::CaseInsensitive))
{
*brush = QBrush(Qt::white, Qt::SolidPattern);
return true;
}
return false;
}
The following user(s) said Thank You: wotalota
Last edit: 2 years 9 months ago by Bart.
2 years 9 months ago #72513

Please Log in or Create an account to join the conversation.

Time to create page: 0.862 seconds