×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

New All Sky camera management software: indi-allsky

  • Posts: 83
  • Thank you received: 4
manually activating the virtualenvironment and issuing the command flask db init or flask db revision --autogenerate results in an illegal instruction error. I believe it should or does execute app.py with no success. Reson might be a flask version not suited for the old processor in my RPI Zero W. Maybe an older flask version or another wheel would do the trick.

CS, Markus
9 months 3 weeks ago #93753

Please Log in or Create an account to join the conversation.

  • Posts: 261
  • Thank you received: 66
I am reading this is apparently a very common problem with armv6l CPUs like those in the Pi Zero. It is possible it is one of the python wheels installed from a arm7l build and is compiled with CPU instructions that are incompatible with your CPU.

If it is related to one of the python modules and you can figure out which one, recompiling that module directly should fix the problem. It is just a matter of finding the binary with the problem.

Unfortunately, I do not have a Pi Zero to test with. I do have a very old Raspberry Pi 1... it looks like it has the same CPU as the Zero, so I will go run some tests.
9 months 3 weeks ago #93763

Please Log in or Create an account to join the conversation.

  • Posts: 261
  • Thank you received: 66
Believe it or not, I found two modules that were causing the segfault on armv6l: cryptography and bcrypt

You can pull down the latest and code and re-run setup.sh or just take this shortcut:

Activate the virtualenv.
pip3 install cryptography==37.0.4 bcrypt==3.2.2
9 months 3 weeks ago #93813

Please Log in or Create an account to join the conversation.

  • Posts: 83
  • Thank you received: 4
Hi Aaron, thank you very much. It seems to work now!!! Will do further testing and reporting.

CS, Markus
9 months 3 weeks ago #93823

Please Log in or Create an account to join the conversation.

  • Posts: 83
  • Thank you received: 4
Raspbian 12 is out and I migrated my Rpi4. I ususally use the build-indi script delivered with indi-allsky to compile indi. Only very minor changes were needed (change 11 to 12 and libdc1394-22-dev is now libdc1394-dev). Ini-core compiles smoothly, with indi-3rdparty the eqmod driver does not link, likely an unrelated problem.

CS, Markus
The following user(s) said Thank You: Aaron Morris
Last edit: 9 months 1 week ago by Markus Kempf.
9 months 1 week ago #94096

Please Log in or Create an account to join the conversation.

  • Posts: 261
  • Thank you received: 66
I will definitely work on the Raspbian/Debian 12 support soon.
9 months 4 days ago #94157

Please Log in or Create an account to join the conversation.

  • Posts: 201
  • Thank you received: 18
I updated indi-allsky along with indilib (2.0.2) last night and now it is not processing images. It does seem to acquire OK:

Jul 24 00:00:24 allsky [INFO] Image-540/MainThread stretch.main() #46: Image str
etching disabled
Jul 24 00:00:24 allsky [INFO] Image-540/MainThread image._convert_16bit_to_8bit(
) #2292: Resampling image from 16 to 8 bits
Jul 24 00:00:24 allsky [WARNING] Image-540/MainThread image.recalculate_exposure
() #1353: New calculated exposure: 15.00000000
Jul 24 00:00:24 allsky [INFO] Image-540/MainThread stars._generateSqmMask() #94:
Generating mask based on SQM_ROI
Jul 24 00:00:25 allsky [INFO] Image-540/MainThread stars.detectObjects() #84: St
ar detection in 0.4205 s
Jul 24 00:00:25 allsky [INFO] Image-540/MainThread stars.detectObjects() #86: Fo
und 184 objects
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker()
#349: Image worker exception: Traceback (most recent call last):
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker()
#349: Image worker exception: File "/home/thomas/indi-allsky/indi_allsky/imag
e.py", line 234, in run
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker()
#349: Image worker exception: self.saferun()
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker()
#349: Image worker exception: File "/home/thomas/indi-allsky/indi_allsky/imag
e.py", line 263, in saferun
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker()
#349: Image worker exception: self.processImage(i_dict)
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception: File "/home/thomas/indi-allsky/indi_allsky/image.py", line 569, in processImage
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception: self.image_processor.label_image()
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception: File "/home/thomas/indi-allsky/indi_allsky/image.py", line 2753, in label_image
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception: self.text_size_pillow = int(self.config)
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception: KeyError: 'PIL_FONT_SIZE'
Jul 24 00:00:29 allsky [ERROR] MainProcess/MainThread allsky._startImageWorker() #349: Image worker exception:
Jul 24 00:00:29 allsky [INFO] MainProcess/MainThread allsky._startImageWorker() #356: Starting Image-541 worker
Jul 24 00:00:29 allsky [WARNING] MainProcess/MainThread image._load_detection_mask() #1362: No detection mask defined
Jul 24 00:00:29 allsky [INFO] MainProcess/MainThread allsky._queueManualTasks() #1111: Checking for manually submitted tasks
Jul 24 00:00:31 allsky [INFO] Capture-1/MainThread capture.saferun() #206: Camera last ready: 7.4s


any ideas
9 months 3 days ago #94175

Please Log in or Create an account to join the conversation.

  • Posts: 261
  • Thank you received: 66
You might just try saving the config in the form without making any changes and then fully restarting indi-allsky.

It should have automatically done that when you re-ran setup.sh, but maybe I messed up something in the logic.

This line is bizarre to me...
Image worker exception: self.text_size_pillow = int(self.config)

That is not how the code should read at all. Perhaps the exception was truncated...
Last edit: 9 months 2 days ago by Aaron Morris.
9 months 2 days ago #94180

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
I have encountered this issue. Can you please elaborate more on what path needs to be written into the script and where?
Thank you
8 months 4 weeks ago #94232

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
I have encountered this issue. Can you please elaborate more on what path needs to be written into the script and where?
Thank you
="Gonzothegreat post=90239" ]Flask command issue.
 
./setup.sh: line 1848: flask: command not found
 
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$ pip3 list | grep -i flask
Flask                  2.2.2
Flask-Login            0.6.2
Flask-Migrate          4.0.4
Flask-SQLAlchemy       3.0.3
Flask-WTF              1.1.1
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$
 
 
RESOLVED:
I've added the direct path to flask in the setup.sh file
Last edit: 8 months 4 weeks ago by Andrew.
8 months 4 weeks ago #94233

Please Log in or Create an account to join the conversation.

  • Posts: 261
  • Thank you received: 66
That is interesting and I am not sure why this would happen.

Within the setup.sh script, it instantiates the python virtualenv, this should prepend the bin/ folder of the virtualenv to the shell's PATH environment.

You did not happen to move the cloned indi-allsky git folder, did you?
8 months 4 weeks ago #94234

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
I did not move it. But I was getting warnings about some things not belonging to PATH. I can look into adding them and try again.
8 months 4 weeks ago #94235

Please Log in or Create an account to join the conversation.

Time to create page: 1.483 seconds