Get Connected!

Come and join our community. Expand your network and get to know new people!

Sorry, we currently have no events.
View All Events

I have been using ASTAP to fine tune backspacing and tilt. You feed it a series of images at different focus positions moving all in one direction to avoid any backlash. It then determines HFR in different regions of the sensor (3x3 grid) and you find the minimum for each region to identify needed adjustments. At the moment I manually set new focus position then capture image, change focus position, capture another image etc. The automatic focus routine isn’t suited because it varies step size and goes back and forth, also doesn’t save the images for later analysis. Is there anyway to automate this in ekos, scan a variable, save images along the way?


So I've compiled the latest stellarsolver (2.2-44_g9d4efa4) and kstars on my Pi4, which I use to control my ASI183MC attached to an old Canon FD 135mm lens. Everything worked very smooth, with a clear AF curve, but when I look at the result, the stars in the red channel look much better than in the green channel, which actually is the worst of all three (IMO).
Not sure though if that has to do with the 'quality' of the lens :(
I'll try an AF run tonight with storing the images (hope I find them...), maybe that tells me more.


Brent created a new topic ' Saving Data' in the forum. 3 hours 43 minutes ago

I am using a ASI AirPro with the SM 1.6.2 OS to do my capture/control in a remote observatory. I am stumped as to how I save my image data to both the default and remote storage device. I know how to get to where to change the settings, but can't seem to find the proper directory to type in the location for the remote storage.

Is it my ineptness of possibly the AirPro being the issue?

Any assistance would be appreciated.



This looks exceptionally pleasant :-) I primarily utilize my all-sky for cloud discovery. Do you've got bolster for may location? I am going to share this thread florida lottery software-indi-allsky.html?start=84 to my kith and kin who want to know about that. I do it by tallying the number of stars, which appears to work lovely well but not 100%....


i met an issue with the scheduler
i want to run a scheduler WITHOUT have to open my roof ( no constraints set).
with my current profile (with aldiroof), if i uncheck unmount dome, roof still opens when scheduler starts.

so i created a new profile, without any dome, and started the schedule. but the roof still opens... :/
it's the same with a dome simulator.

i tried with a total profile with simulators , each time I start a schedule, the roof is opened...

Why is that a real problem ? ^^'
because i managed to restart ekos when weater becomes better , i found a way to force flat frames even if the 1ts schedule is stopped by clouds.
not very clean (mqtt , ssh , node red , sh and ekos , but i'm not good at programming ^^'

but that the roof opens whatever the current weather is verry annoying (and dangerous) , and I need to start flat schedule even when it's raining

How can i enforce the roof to be close when i start thoses .esq ?

thx :)


Applying Pythagorean Theorem, your circular FOV is 13.47' . So first of all, you need to see if you've got the index-4205-*.fits. Look at Align/Options/Index files for this. Eventually download it. That said, this field is VERY small so chances are you won't have enough stars in your image to solve your position, except maybe if you're pointing at some object inside the Milky Way.
There nothing to do with this, it's not a bug and you're not responsible. Try with a camera with a larger FOV and it will work fine. I have a Celestron C11 XLT (same focal lengh) and it solves perfectly with my ASI1600.

- Marc


Ed Lee replied to the topic 'Problems with unit tests' in the forum. 7 hours 50 minutes ago

Thanks Hy. Glad it's not me.



When I run unit tests locally, I find I often have to run them in their $BUILD/Tests/$TEST_DIR directory.
So, for instance, in my case that would be:

cd ~/Projects/kstars-build/Tests/polaralign

I'm honestly not sure what the testing environment does when it runs its testing pipeline.
You can see a pipeline output, for instance, by looking at the pipeline link in an MR.
Here's my latest MR:
and you can see a pipeline link on that page, which is also here:
You should see that my MR passed all the "stable" tests, but had some issues with tests marked "unstable".

Interestingly, I didn't see any reference to TestFitsData in the pipeline output, not sure why.
I just tried to run that test, and also got failures, so it isn't you.
Clearly we need to look at it. Someone must have disabled it.
Don't have time to look right now.

Be aware that we don't have great test coverage, though it has been improved in the past year. It is certainly an area that would be great to improve.

Thank you for looking into things, and looking forward to see what you come up with.



You and ASTAP have made my day :)

I could not find that in the manual but it is a fantastic feature.



1. Open the stack window
2. Load the files needed to edit header.
3. Click the left mouse button to select the first file.
4. Hold Shift and left click on the last file (all files should become highlighted)
5. Right-click any highlighted file and select Change Keyword in Selected Files/Enter Keyword and New Value from the pop-up menu.
6. In the first modal window, enter OBJECT and click Ok.
7. in the second modal window, enter the name of the object and click Ok

This way you can edit any header in FITS-file



ASTAP is one of my favourite programs but I wasn't aware that it could edit the header for individual files let alone as a batch.

How do you do it?



amerigo voyage has liked amerigo voyage's Profile 13 hours 55 minutes ago