Good advise from phomer60. You can "abuse" the Object Name field for this. I suppose that this is for quick inspection of the files because the temperature info is added to the headers of the images (either FITS or CR2 in case of a Canon DSLR) so the info is available.
thank you for the answers. I am aware that I can set a prefix or look at the FITS header, but that's not really what I am after.
The capture module seems to support scripts, I guess I could use astropy's fits package to get the required information from the header and write my own filename.
Anyway, it would be nice to expose the different variables inside EKOS to build a custom String, like %OBJECT_%FILTER_%EXPOSURE_%GAIN_%TEMP_%FRAME.fits
Yes that's an excellent idea, but it appears no one had time to implement this since there are some many dependencies on the naming scheme when executing jobs. PR are most welcome!!
One other thing to add. I find that I have sequences I've stored that I could reuse for many imaging session, if it were not for the Prefix and Directory fields.
So, putting wildcards in both would be great for me, and, what's I'd like is a special wildcard that could be set outside the script, for the current session.
E.g. I might have a standard script that runs through R,G,B filters for 240s exposures. Perhaps I could use the same script for M31 and M33 on different nights
by somehow setting a $NAME variable somewhere, and in the Prefix box use simply "$NAME" and in the Directory box, something like "/home/pi/Pictures/$NAME".
Not sure where to put the ui box to enter $NAME. The capture tab is a candidate, but that would preclude using the scheduler with the same script for two different objects on the same night.
Also, Sven, please take a crack at it, but if you decide not to do it, let me know and I'll try.
Hy