I see there are a few tokens (`_[DHTF]_`) that can be used to construct a capture path, but it doesn't appear that there are ones for object name, camera, etc. I'd like to be able to do any combination of

_D_ - date
_H_ - time
_T_ - timestamp
_F_ - filter (frequency for the radio astronomers?)

_C_ - camera
_S_ - scope/source/sensor
_O_ - object
_N_ - exposure number
_X_ - exposure length
_I_ - image type (flat, light, dark, ...)
_L_ - other lenses (barlow, reducer, corrector, ...)
_G_ - gain

so I could say my output path is something like:

/mnt/astro/_C_/_O_/_K_/_F_/_O_ _K_ _T_ _N_.fits

The point of this is to allow the capture to be automatically aggregated in more meaningful ways.

* one might leave this set up for weeks at a time and just drive it around for a bit of EAA-style astro(nomy|photography)
/mnt/astro/SV503-SV193-LPro-ZWO_ASI533MC/M42/Light/30_secs/M42_2022-03-17T20-48-39.fits

* one might have more sophisticated setup including an EFW to swap filters, so it wouldn't make as much sense to embed the filter name into the scope/camera part of the path ...
/mnt/astro/NP127-ZWO_ASI2600MM/M42/Light/Ha/30_secs/M42_2022-03-17T20-48-39.fits

Also I couldn't find a way to make the output path be consistent between the capture module and the scheduler; if I'm just capturing, images go to /home/stellarmate/Pictures/Light/<filter>/<generatedfilename>.fits; the scheduler puts them under /home/stellarmate/Pictures/<target>/... - it would be nice to make these do the same thing.

Read More...

That's not lazy enough. It works when I remember to confirm the filter selection, but I'd rather not lose imaging time because I forget to. There are other dialog boxes that are automatically dismissed after some time - I'd like the same to happen when the scheduler runs.

I additionally tried setting/saving it in my device profile as the default but that confirmation isn't preserved across an INDI restart (like every time kstars crashes).

Read More...

So I had a sequence set up for last night and lost a couple of hours of imaging time since the sequencer was waiting for me to confirm that the filter was properly set. I don't actually have a manual filter wheel but it's convenient to use the manual filter wheel to say "in my optics bag I have UVIR, Neodymium, UHC, CLS, LPro, LXtreme ... and until further notice I'm using the ... LPro". Then all of my file names and metadata correctly indicate what filter I'm using.

It would be nice if the sequencer would confirm right away when I hit the start button; or the alignment and capture modules could confirm earlier that my manual filter is correctly set. Perhaps they could be set to time out after a configurable interval and trust that I have my optics set up as desired.

Read More...

Chris Kuethe replied to the topic 'Live Stacking Issues' in the forum. 2 months ago

Happens on Android too.

Read More...

Goodness no, do not edit cmakelists unless you're a developer or you can explain why you need to do it and can demonstrate that there is a no better way.

There is, in fact, a better way. You can read through cmakelists to figure out which flags to use to enable/disable certain features, or use ccmake (sometimes called cmake-curses-gui) to interactively select them... I'm lazy and prefer the latter.

You can easily mount an sdcard somewhere, check out the source and compile it, then install to a completely different path. That is one of many things you can configure with cmake (or ccmake). On my Radxa I mounted the sdcard on /mnt/sdcard, put the source in /mnt/sdcard/src/indi, deactivated some drivers I didn't need, compiled in /mnt/sdcard/build-indi, and installed to /usr/local.

Read More...

Hm. That seems to be a very low power machine. Things you might want to try:
- enable zram for swap. it'll be faster than swapping to sdard/emmc
- do all the compiling on the sdcard. It won't be fast, but at least it's got lots of storage
- compile only the necessary drivers
- cross-compile on a much faster amd64 machine

At the moment, I'm compiling indi and kstars on a Radxa Zero, with all the source on a microsd...

Read More...

The ability to load and slew is great, I've been using it heavily for the past month to manually run capture jobs for long-running projects.

Unfortunately I don't see a way to load and solve an image to schedule a job. Basically I'd like to load up a couple of FITS files and say "after astronomical twighlight, keep accumulating light for on top of this photo for a while.  Once you've completed that (or when you lose guiding), start accumulating light for this other photo until dawn." I know I can define a job with coordinates, but letting the plate solver do it for me would be nice.
 

Read More...

Chris Kuethe replied to the topic 'Thoughts on the dark library' in the forum. 4 months ago

Yes, I already built a small dark library by running a series of dark sequences with my most common capture settings, then stacking them with siril... But this seems like something that could be automated even more. Putting button for the dark library on the CCD tab (not just the guide/solve tab) suggests to me that the automated dark library is intended for use with imaging too.

Read More...

Chris Kuethe created a new topic ' Thoughts on the dark library' in the forum. 4 months ago

So the universe is clearly angry at me for stealing too many photons last night and it's blessed me with clouds tonight. Fine, I needed to expand my dark library anyway. Here are some thoughts I had while doing that.

  • If I have multiple cameras, I should be able to run the dark library tool in parallel for each of them, eg. guide camera and imaging camera.
  • I'd like to keep the generated dark library someplace it can be shared (eg. a network drive) among various rigs. Yes, I've also got a dark library on my network share that I can use with Siril, but it's nice to let Ekos do some of that work for me.
  • I'd like to be able to use bigger intervals. Right now it seems I can go up to 20s steps; once I get to a couple of 120s or 180s exposures I'd prefer to be able to increase by up to 60s for the generated dark sequences
  • Dark library manager (DLM) limits me to collecting 20 darks for a given exposure range. Why not let me take as many as the sequencer would allow lights? This would probably help in compensating the bias too, right?
  • DLM doesn't show me other capture parameters, eg. gain or offset.
  • The CCD column isn't useful given that I already know what camera I'm operating on because of the drop-down
  • DLM doesn't let me choose what gain(s) to use
  • DLM doesn't let me multi-select and delete a bunch of darks that I didn't want
  • DLM doesn't preserver sort order when deleting entries
  • DLM can't sort by multiple columns, eg. first by duration and then by temperature


Read More...

Chris Kuethe replied to the topic 'KStars & Ubuntu 21.10?' in the forum. 4 months ago

It works fine for me. You might want to use the PPA rather than the version that ships with ubuntu though - it's really old and missing a lot of features from newer releases.

Read More...