Hy Murveit replied to the topic 'Internal guider store 2 calibrations' in the forum. yesterday

Steve,

It is not implemented, but would be reasonably straight-forward.

I'll take a look,
Hy

Read More...

I would have expected those changes to be in version 3.4.3.
They were submitted to the repo 2 days before the 3.4.3 cut was made, however, I only run from latest source, so I can't attest to that.
Perhaps you're not getting the 3.4.3 release in whatever distribution you're using for Raspbian?

The code was submitted on July 16 and it looks like the release was made on the 18th.

commit 548752fd6f098a8208bb82420ae7cba043fd9250
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Sat Jul 18 10:28:53 2020 +0300

3.4.3 changelog


commit 35c4da72b471db2b3ef85243e7d38099f4456efe
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Sat Jul 18 10:22:19 2020 +0300

INDI driver sync

commit 9149bd08083f4260dd1d216edf09957dac2f5547 (origin/guider-fix1, guider-fix1)
Author: Hy Murveit <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 00:04:58 2020 -0700

Enforce reticle for MultiStar-findGuideStar, dither from reticle, reset MultiStar on abort.

commit bf439ae5e11b57edabd9a25bbf50fc0536d51b45
Author: Cyril Richard <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 17:24:31 2020 +0000

Update fits viewer following the add of the new ROWORDER in libindi ( github.com/indilib/indi/commit/176173ed5...b8881c67b335fc570b34 )

commit ff8aa89a09be136fb86d669082c970c0377b168b
Merge: 11130020b 19ec71c74
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 10:23:59 2020 +0300

Merge branch 'edejouhanet/kstars-bugfix__focus_tests'

commit 11130020b83497e98efaf5ace4fc892283abf652
Author: Eric Dejouhanet <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 07:21:47 2020 +0000

Bugfix phd2 protocol tolerance

commit 19ec71c74abda71182340b23b5f33eddc1c2d689
Author: Eric Dejouhanet <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 07:54:07 2020 +0200

Fix qCompare int/double.

commit 29abc4aefee7ed16bcba94e08f0f641b2a32600c
Author: Eric Dejouhanet <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Fri Jul 17 00:48:14 2020 +0200

Fix focus test missing header.

commit 009c0738f09faf70d730a96da7781d9b44f7f12e
Merge: 4fc154588 2c4aab15d
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Thu Jul 16 10:30:19 2020 +0300

Merge branch 'murveit/kstars-reuse-calibration'



Read More...

Hy Murveit replied to the topic 'New User - A speed question' in the forum. 2 days ago

Peter,

Try a couple things.

1- Try downsampling your image. I tend to downsample by 3 I believe, though not sure. See the "Bin" dropdown, which is the 4th to bottom line on the Align page.
In the Options (bottom right) of that page, under solver options, you probably want "Use Position" "Auto Update", and also "Downsample, 2, Auto". Also "Use Scale" and "Auto Update" that too.
Keep on using the local version. Using the online version is slow in my experience.

2- Also try to use ASTAP (see www.hnsky.org/astap.htm to install)
Either one should work faster than what you have.

If these don't work, can you send a picture of your "Solver Options" pop-up, and your Align Page?

Hy

Read More...

Scott,

Sorry that it's not obvious. It's in the calibration settings.

You go to the guider tab, click on the Options in the bottom right corner, then click on the Calibration section (near the upper left of that popup), and then the checkbox is the bottom checkbox on the pop-up page.



Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Jo,

I don't know what would happen if you set it to 10000ms, but clearly that won't speed things up,
rather it will likely slow things down. It will probably guarantee that each iteration is a minimum of 10s long.
If I were you, I'd use a "normal value" like 500.

In general, please be conservative with changing all these various parameters.
Trying to save a few seconds here and there can cost you (and me) hours of debugging...

Hy

Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Jo,

1- I don't have a recommendation on the pulse size. You're probably right that 2000ms is excessive. Probably 500 - 1000 would make more sense, but just guessing.
FWIW, It doesn't actually fit a line, as it currently stands. It just draws a line between the first and last point. That's probably fine, but let me know if you disagree.

2- With respect to Jean-Claude crossing 25 on DEC (the vertical blue dots), I looked at that too when I first saw his plot, but you have to remember that it doesn't start a zero.
First there is some "backlash-clearing" movement. So, it looks like the backlash section (vertical while +'s) ended between 5-10 so it does make sense to me.

Hy

Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Jo,

You are mistaken here. When you set it to 10 iterations, it uses UP TO 10, but once it crosses 15 pixels of movement it stops.
I could make that "15 pixels" a parameter some day, but we have so many already...
So, you can see that even though he had 10 set, the movement was sufficient in both axes to terminate the calibration after 3 or 4 steps.
[This was a change I made in the last few months, so you're probably relying on older experience with the calibration.]

Again, I recommend setting the number of iterations on the maximum (10) and letting is stop itself after 15 pixels of movement.

Hy

Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Hy, everyone

Would it be useful to have a list of mounts and whether the reverse Dec is needed? E.g.
Indi-eqmod: unchecked
Indi-whatever the op used: checked
etc...

Cheers,
Steve


Steve,

It is the same concept as the "Reverse Dec ..." parameter in PHD2.
One could look at their doc, e.g. github.com/OpenPHDGuiding/phd2/wiki/Reve...-after-meridian-flip
but I can't verify this.

Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Jean_Claude,
That calibration (and guiding) looks great to me.
Hy

PS That other thing on your screenshot (how you lost track of the guidestar right after starting to guide) happens to me too :( I assume you're running the scheduler, and that what happens is it starts guiding, then interrupts guiding right away to focus. I've looked at the images and during my initial focusing, sometimes particularly at the start, it seems to "move the image" significantly. The result is that you may guide well, but your image is moved a bit from where the alignment put it. Is that your situation too? If so, curious what mount and focuser you have.

Read More...

Hy Murveit replied to the topic 'New Internal Guider Features' in the forum. 4 days ago

Sure, see this screenshot.
You go to the guider tab, click on the Options in the bottom right corner, then click on the Calibration section (near the upper left of that popup), and then the checkbox is the bottom checkbox on the pop-up page.



Read More...

Hy Murveit replied to the topic 'Help For INDI Website' in the forum. 4 days ago

It seems that the link to 'KStars API' under 'Resources' on edu.kde.org/kstars/ is broken.
Hy

Read More...

Hy Murveit replied to the topic 'Dark Frame Subtraction in the Internal Guider' in the forum. 7 days ago

Wouter,

That is disappointing. sep_extract() is currently run with a 10-pixel minimum area for detecting stars--that 10 is not the area inside the HFR,
it is wider than that, I suppose meaning 10 pixels above the background level. See:
invent.kde.org/education/kstars/-/blob/m...sepdetector.cpp#L147
where the 4th arg, 10, is min_area:
invent.kde.org/education/kstars/-/blob/m...iewer/sep/sep.h#L219
Perhaps your system was fooled by some poorly calculated background level. In any event hopefully
Rob's upcoming SEP update, scheduled for 3.4.5 will have better optimized SEP parameters.

I did try to improve guide-star selection in the SEP MultiStar scheme. There it tries to select stars with the highest SNRs
(up to an SNR of 100). You might try to guide with SEP MultiStar to see if it improves things, if you aren't already.

If you have any guide images that are fooled by hot pixels, I'd love to check them out.

Hy

Read More...

Hy Murveit replied to the topic 'How Update Kstars on Astroberry RPi4' in the forum. 7 days ago

David (@wornish):

I didn't check your dependencies etc carefully, but a few comments on your compile instructions:

1- The KStars README.md file invent.kde.org/education/kstars/-/blob/master/README.md also gives compile instructions.

2- For the kstars cmake command, you should probably add -DCMAKE_BUILD_TYPE=RelWithDebInfo
That gets the compile to run 'optimized' which for several operations makes the executable run much faster (though it probably slows
down the compile). I believe it defaults to Debug/not-optimized.

3- When you run your make, you should add -j6 or -j8. The '6' version means "if possible run up to 6 compiles in parallel" which is usually
fine on an RPi4 with 4Gb of memory. You'd run -j8 on a faster machine with more memory. You can experiment with the number.
(On an old Rpi3, I'd stick with the way you have it, equivalent to -j1). So the command would be "sudo make -j6 kstars". You'll still need to
"get a cup of coffee" but a compile from scratch will take ~40 minutes instead of 2-3X that.

Hy

Read More...

Hy Murveit created a new topic ' Dark Frame Subtraction in the Internal Guider' in the forum. 7 days ago

I was recently thinking about the dark-frame subtraction option in the internal guider.
As I understand it, if checked, Ekos will capture a single dark frame exposed at the guider's selected exposure duration,
store that dark image, and later subtract that dark image from every future guider capture, performing the guider's
usual signal processing on the dark-subtracted guide image.

I'm posting because it seems to me that this might not be a good idea (i.e. subtracting ONE dark frame capture from the guide image).
I believe it likely introduces noise into the guide image, and may cause more harm than good.
One could reduce the amount of added noise, e.g. by capturing 5 or 10 dark frames, averaging them, then subtracting the average frame
instead of subtracting a single sample, but there will always be more random noise in the dark-subtracted guide frame, than the original guide frame.

I believe the reason to do dark subtraction, in spite of possibly increasing noise, is to try and remove some of the fixed pattern noise
from the guide frame, as well as removing hot pixels. Hopefully detection schemes like SEP are not too sensitive to hot pixels, and less sensitive
to the fixed pattern noise (they're trying to detect guide stars, not make pretty pictures), but perhaps "it wouldn't hurt to remove it any may improve
star detection in certain circumstances".

What do folks think?
- Is there a benefit to dark frame subtraction in the guider?
- Does it make sense to subtract a single dark frame?
- Would it be worth it to average N dark frames and subtract those from guide frames?

Hy

Read More...