![]() ...
·
![]() |
---|
I am having an issue initializing the script for the first time. I keep getting an error: python AstroBinUpload.py Traceback (most recent call last): File "c:\Users\Daniel\Desktop\AstroBinUploader-1.3.10\AstroBinUpload.py", line 281, in <module> main() ~~~~^^ File "c:\Users\Daniel\Desktop\AstroBinUploader-1.3.10\AstroBinUpload.py", line 132, in main output_dir = sys.argv[1] ~~~~~~~~^^^ IndexError: list index out of range |
![]() ...
·
![]() |
---|
Daniel Carter: I also get the same error when I try to run it for the first time, and with no generated config.ini file the script doesn't work. |
![]() ...
·
![]()
·
1
like
|
---|
Daniele Borsari:Daniel Carter: Try running this from the command line from inside the folder where the script is downloaded: python AstroBinUpload.py "\" That gives the script a directory to look at where the configuration should be written (the slash may be the other way if that doesnt work....I cant remember which way the slash should go). |
![]() ...
·
![]()
·
2
likes
|
---|
@Daniel Carter Thank you! It worked perfectly. Actually the slash was the other way just to let you know. Daniele |
![]() ...
·
![]() |
---|
Daniele Borsari: Good deal! I'm glad it worked out for you. The previous versions of the script created the output files in the folder where the script was located. This new version creates the output files in the folder you are reading from. So if you are looking for the output files, they are in your folder you target in the script. |
![]() ...
·
![]() |
---|
Hi Daniel and Daniel, Thanks for finding this bug. The situation at the moment is: 1. Run from installation directory with no config file and no arguments passed : -error, as you have found. 2. Run from installation directory with no config file and arguments passed : script exits and asks user to modify config 3. Run from installation directory, config file exists and arguments passed : script runs 4. Run from any other directory with no arguments passed : script exits with indication that arguments are needed 5. Run from any other directory with '.' passed as the first argument but no config file : script exits and ask user to modify config 6. Run from any other directory with '.' passed as the first argument, config file exists : script runs I will rectify this in my next release. Thanks and CS |
![]() ...
·
![]() |
---|
Daniele Borsari: So, actually what I'd like to be different from the current version is just the working mode for the date separation to use the -12 hours function. I can easly edit the csv file to remove unnecessesary (to me) information, but that's it. Daniele |
![]() ...
·
![]()
·
2
likes
|
---|
Update 28th October 2024 I have just released the latest version of the script. v1.3.11V1.3.11 changes 1.0 Fixes bug where running the script for the first time from the installation directory would fail 2.0 Deals with the case where the filter names in the light frames have trailing white spaces. 3.0 Modified the script to take a new default parameter for the config file: The parameter is USEOBSDATE and if set to True, the actual date of the observation session is used when aggregating data for the Astrobin .csv output. If this parameter is set to False, then the date the observation session was started is used. 4.0 Added progress counter to the HFR processing section of the screen output The USEOBSDATE was introduced to allow all images captured during a session to be associated with the start of the session. The current behaviour is to associate the image with the date of capture. To use the script in this new mode set USEOBSDATE = False in the config.ini file. This can be placed in the [defaults] section, an example is given below: [defaults] #FITS keyword Default value IMAGETYP = LIGHT EXPOSURE = 0.0 DATE-OBS = 2023-01-01 XBINNING = 1 GAIN = -1 EGAIN = -1 INSTRUME = None TELESCOP = None FOCNAME = None FWHEEL = None ROTATOR = None XPIXSZ = 3.76 CCD-TEMP = -10 FOCALLEN = 540 FOCRATIO = 5.4 SITE = Papworth Everard SITELAT = 52.2484 SITELONG = -0.1231 BORTLE = 4 SQM = 20.5 FILTER = No Filter OBJECT = No target FOCTEMP = 20 HFR = 1.6 FWHM = 0 SWCREATE = Unknown package USEOBSDATE = TRUE I have added a progress counter that appears as the HFR values are being calculated, it seems some of you process such large image data sets that you were not sure if the script had hung or not! A comment based upon some user feedback: 1. If the script does not find the filter name that is used in the fits headers in the config file then it will use the filter name found in the header in the astrobin .csv file. You need to ensure the filter naming convention used in the header file exists in the config file, along with the code for that filter. CS Steve The scripts can be found here https://github.com/SteveGreaves/AstroBinUploader The release bundle can be found here https://github.com/SteveGreaves/AstroBinUploader/releases/tag/v1.3.11 *********************************************** |