hypernets / hypernets_tools Goto Github PK

Dear @corizzi and @saberioon,
How can we access the webcams remotely? Which scripts were you referring to in the last WP345 meeting?
Thanks

Hi Alex,
As discussed yesterday it will be nice to have the following features for the system:

1. "no go zone"
   Set for instance angles for which no measurements need to be taken from 256degrees to 82 degrees

2. check best angles
   For water we usually measure at 90degrees (AERONET-OC procotol) and/or 135 degrees (TriOS Protocol). According to the sun azimuth and the no-go zone we could have a script to check which angles (e.g., 90deg, 135deg, 225deg, 270deg... it could be others in the future if processing improves) does NOT fall into the no-go zone and/or shadow and rewrite the sequence file accordingly before running the sequence (e.g. this script will be called within run_sequence?).
   I can surely help with this!

Thanks!
Clémence

Dear @corizzi,

• I was able to set up the cameras using a Windows machine. So, we have a username and a password for each camera. Looking the "webcamGetImg.sh" script, it seems that the credentials for the cameras needs to be passed as:

credentials=USER:PASS

and therefore, in the config file:

webcam_sky = USER:PASS@ip_cam_sky
webcam_site = USER:PASS@ip_cam_site

Am I right?

• Also, should the IP addresses assigned to the cameras be related to the family of IP addresses assigned to the Yoctopuce?

• We are assuming that we need to input the rugged-PC Wifi Hotspot credentials when we are close to the Studiel box but using the Windows machine with the software. Right?

Hi @corizzi

Is there any command to terminate a sequence in the middle of it ?

sequence service is interrupted with this error

run_service.sh[2264]: init error:ytcp:648:tcp(111):Connection

However, I can ping the yoctopuce.

Besides rebooting the system manually, is there any other solution available to fix this issue?

I encounter the below error when I try acquisition

VNIR Irradiance 16 0 1 0 2592 x 1944, 5MP
--> [VNIR IRRADIANCE 16 0] x 1
/dev/ttyUSB5: No such file or directory

LibHypstar::linuxserial::linuxserial(int, const char*): serial port open failed.
/dev/ttyUSB5 port open failed

Error : unidentifiable C++ exception

also, following error box appears:

Any advice to fix it?

Hello @corizzi! (All!)

I am trying to take a measurement using the new GUI, but I am getting the error:

--> [VNIR IRRADIANCE 32 0] x 1 Spectrum #0 added Error : [Errno 2] No such file or directory: 'DATA/20210129T152920_VNIR_Irr_00032_00000_01.spe

I am running the GUI from the rugged PC for now.

I attached a screenshot of the error.

What am I missing?

status of systemctl for hello service is show failing system:

● hypernets-hello.service - Hypernets Sync Config Server and Send Data
     Loaded: loaded (/etc/systemd/system/hypernets-hello.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-03-01 16:06:32 CET; 1min 43s ago
    Process: 1034 ExecStart=/home/gfz/Downloads/hypernets_tools/comm_server/hello_server.sh (code=exited, status=255/EXCEPTION)
   Main PID: 1034 (code=exited, status=255/EXCEPTION)

Mär 01 16:06:02 gfz-pc1 systemd[1]: Started Hypernets Sync Config Server and Send Data.
Mär 01 16:06:02 gfz-pc1 hello_server.sh[1034]: Sleep 30 sec
Mär 01 16:06:32 gfz-pc1 systemd[1]: hypernets-hello.service: Main process exited, code=exited, status=255/EXCEPTION
Mär 01 16:06:32 gfz-pc1 systemd[1]: hypernets-hello.service: Failed with result 'exit-code'.

Originally posted by @saberioon in #8 (comment)

Because issue #8 closed, I open this issue to follow up on the syncing issue

@corizzi,
I have noticed that every time you do a new commit to the VEIT branch, the rsync with the server stop working. It seems that because our branch in the rugged-PC is behind a commit, the rsync of the DATA does not work. So far, I have been solving it by git stash and then git pull from the rugged-PC. Is this a normal behavior?

@corizzi, All,
Does anyone experience this issue?

When following the instructions:

Try to start and watch what happens with :
sudo systemctl start hypernets-sequence
ournalctl -u hypernets-sequence --follow

I am getting the following error:

[hypernets@hypernets-cnr1 hypernets_tools]$ sudo systemctl start hypernets-sequence
[sudo] password for hypernets: 
Warning: The unit file, source configuration file or drop-ins of hypernets-sequence.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[hypernets@hypernets-cnr1 hypernets_tools]$ systemctl daemon-reload
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ====
Authentication is required to reload the systemd state.
Authenticating as: admin (hypernets)
Password: 
==== AUTHENTICATION COMPLETE ====
[hypernets@hypernets-cnr1 hypernets_tools]$ journalctl -u hypernets-sequence --follow
-- Journal begins at Tue 2020-09-22 19:07:01 CEST. --
feb 24 15:16:24 hypernets-cnr1 systemd[1]: Started Hypernets Sequence Service.
feb 24 15:16:24 hypernets-cnr1 systemd[1428]: hypernets-sequence.service: Failed to determine user credentials: No such process
feb 24 15:16:24 hypernets-cnr1 systemd[1428]: hypernets-sequence.service: Failed at step USER spawning /home/hypernets/hypernets_tools/run_service.sh: No such process
feb 24 15:16:24 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=217/USER
feb 24 15:16:24 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.

VNIR Irradiance 8 8 1 0 2592 x 1944, 5MP
--> [VNIR IRRADIANCE 8 8] x 1
Spectrum #0 added
Saved to DATA/20210125T142829_VNIR_Irr_00008_00008_01.spe.
Integration Times : VNIR : 8 ms
: SWIR : 8 ms
Total Dataset Length : 4131
Spectrum Type Information : ('VIS', 'IRRADIANCE')
Timestamp : 1970-01-01 02:45:25
Exposure Time : 8
Temperature : 33.523780822753906
Pixel Count : 2048
mean X : 0
std X : 0
mean Y : 0
std Y : 0
mean Z : 0
std Z : 0

I have checked time and date on rugged PC and it is
Local time: Mo 2021-01-25 15:25:17 CET
Universal time: Mo 2021-01-25 14:25:17 UTC
RTC time: Mo 2021-01-25 14:25:16
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

Any suggestion for fixing it ?!

We have updated the tools to the latest main code and the Yocto firmware. Yesterday we left the system in the lab to measure today in autonomous mode. Today we connected remotely to the pc and we found that 4 measurements were acquired correctly

drwxr-xr-x  3 iafe1 iafe1 4096 mar  4 13:01 SEQ20210304T130128
drwxr-xr-x  3 iafe1 iafe1 4096 mar  4 14:01 SEQ20210304T140130
drwxr-xr-x  3 iafe1 iafe1 4096 mar  4 15:07 SEQ20210304T150702
drwxr-xr-x  3 iafe1 iafe1 4096 mar  4 16:01 SEQ20210304T160154

But in the next sequence we got this error

mar 04 16:10:46 iafe1-pc systemd[1]: hypernets-sequence.service: Succeeded.
-- Boot e3041abf417e433086e8a6a954e59213 --
mar 04 17:00:55 iafe1-pc systemd[1]: Started Hypernets Sequence Service.
mar 04 17:00:55 iafe1-pc run_service.sh[943]: Waiting for yoctopuce...
mar 04 17:00:55 iafe1-pc run_service.sh[943]: Ok !
mar 04 17:01:14 iafe1-pc run_service.sh[952]: init error:Invalid WebSocket header (ytcp:2985)
mar 04 17:01:14 iafe1-pc systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=1/FAILURE
mar 04 17:01:14 iafe1-pc systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.

The folder have been generated but after 25 min (1726).

drwxr-xr-x  3 iafe1 iafe1 4096 mar  4 17:26 SEQ20210304T**172648**

Could this error be due to the measurements taking too long to finish?

Unintentionally I have upgraded Manjaro, which lead to the upgrade of Python to version 3.9.1. Afterward, hypernets_tools is not working. Besides downgrading to version 3.8, any other solution available to fix it?

I suggest reversing the tilt direction
tilt = -tilt

This way all view angles from 0 (nadir) to 180 (zenith) are accessible without reversing the direction and the instrument is looking away from the cables exiting from the pan-tilt and the junction box on top of the pan-tilt. In the current code moving from 140 to 180 actually means 320 degrees movement in the opposite direction (if tilt offset is -30).

Hi @corizzi,

I have tried this command to check the status of relays, but it is not generating any output.
python -m hypernets.scripts.relay_command -g

Any advice?

@corizzi,

On the beta branch, The relay script does not give an output when we try to get the status of a relay using -g -nN. It used to give the status ON or OFF of the relays before with main branch.

Luis and @javierconcha

We have extended the cable today and when I run the service, I have receive the following error :

Waiting for yoctopuce...
Ok !
[2, 3]
Sleeping 17s... (old firmware issue)
hypernets/resources/sequences_samples/sequence_land_STD.csv
SWIR:True, park:False
[INFO]	[2021-05-06T12:51:28] Creating serial port (baud=115200, portname=/dev/radiometer0)
[INFO]	[2021-05-06T12:51:28] Got serial port
[ERROR]	[2021-05-06T12:51:29] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:51:29] Received less than 3 bytes (0)
.
.
.
[ERROR]	[2021-05-06T12:52:13] Got baud rate 0
[ERROR] Did not get instrument BOOTED packet in 30s
Hysptar scheduled job exited with code 27

I have tried this treat which works last time when I had the same error. but still, receive this error .

nd_STD.csv
SWIR:True, park:False
[INFO]	[2021-05-06T12:47:36] Creating serial port (baud=115200, portname=/dev/ttyUSB5)
[INFO]	[2021-05-06T12:47:36] Got serial port
[ERROR]	[2021-05-06T12:47:37] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:47:37] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:47:37] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:47:37] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:47:37] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:47:37] Did not get response from instrument, will try different baud rates
[ERROR]	[2021-05-06T12:47:37] Trying baud rate 115200
.
.
[ERROR]	[2021-05-06T12:47:43] Got baud rate 0
[INFO]	[2021-05-06T12:47:43] Creating serial port (baud=115200, portname=/dev/ttyUSB5)
[INFO]	[2021-05-06T12:47:43] Got serial port
[ERROR]	[2021-05-06T12:48:14] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:14] Did not receive BOOTED packet from the instrument during 30.00s
[INFO]	[2021-05-06T12:48:14] Creating serial port (baud=115200, portname=/dev/ttyUSB5)
[INFO]	[2021-05-06T12:48:14] Got serial port
[ERROR]	[2021-05-06T12:48:15] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:15] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:15] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:15] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:15] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:15] Did not get response from instrument, will try different baud rates
[ERROR]	[2021-05-06T12:48:15] Trying baud rate 115200
.
.
[ERROR]	[2021-05-06T12:48:20] Trying baud rate 8000000
[ERROR]	[2021-05-06T12:48:21] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:21] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:21] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:21] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:21] Received less than 3 bytes (0)
[ERROR]	[2021-05-06T12:48:21] Got baud rate 0
[ERROR] Did not get instrument BOOTED packet in 30s

output of this command ls -l /dev/radiometer0:
lrwxrwxrwx 1 root root 7 6. Mai 13:30 /dev/radiometer0 -> ttyUSB5

After I updated the libhypstar to 0.2.2 I am getting this error and it stuck on Trying baud rate 6000000 :

Waiting for yoctopuce...
Ok !
[2, 3]
Sleeping 17s... (old firmware issue)
hypernets/resources/sequences_samples/sequence_land_STD.csv
SWIR:True, park:False
[DEBUG]	[2021-05-10T11:01:21] LibHypstar driver v0.2.2 (commit #4a485fc)
[INFO]	[2021-05-10T11:01:21] Creating serial port (baud=115200, portname=/dev/radiometer0)
[INFO]	[2021-05-10T11:01:22] Got serial port
[INFO]	[2021-05-10T11:01:23] Did not get response from instrument, will try different baud rates
[INFO]	[2021-05-10T11:01:23] Trying baud rate 115200
[INFO]	[2021-05-10T11:01:24] Trying baud rate 460800
[INFO]	[2021-05-10T11:01:25] Trying baud rate 921600
[INFO]	[2021-05-10T11:01:26] Trying baud rate 3000000
[INFO]	[2021-05-10T11:01:27] Trying baud rate 6000000

@corizzi or @jkuusk Any advise ?

Hi @corizzi ,

How to connect to the server for transmitting data automatically? I understand that the config file has the address and name of the folder for storing data but what about the password? Also How to force to upload data? Probably you write it somewhere but I couldn't find it. Your advice is appreciated

We would like to request an option to add a prefix to the webcam files:
From:
"$OUTPUT_DIR/$DATE.jpg"
to:
"$OUTPUT_DIR/$PREFIX_$DATE.jpg"

This would help to differentiate the files from the two webcams without the need to preserve the directory structure.

Hi @corizzi @javierconcha @vitbrando

I try to solve the bugs with the processing of VEIT and found that one of them is related to the fact that I have negative values for the absolute zenith angle (see below pt_abs)... I thought this was not possible... (zenith angle, θv , between 000 and 180° [format: 000.0])... See also pt_ref below is 340.31°?
was the last decision not that pt_abs should be absolute with North (see mails with @corizzi from 06/04/2021...) ?

[01_009_0270_2_0040]
01_009_0270_2_0040.jpg=20211010T061741
pt_ask=270.00; 40.00
pt_abs=378.96;-20.00
pt_ref=19.08; 340.31

Note I also see in the config log:
offset_pan = 0
offset_tilt = +60
azimuth_switch = 215
but this is not documented in the user guide (see D4.7 from July 2021)?

Can you help with this? I'm confused ...
Thanks!
Clémence

Hi @corizzi

I have enabled the systemctl yesterday, but when I check its status today it shows me, system activated at 5:28 am !!! this is its output. I have setup waking conditions from 9 till 17 every 30 min.

lines 1-16/16 (END)...skipping...
● hypernets-sequence.service - Hypernets Sequence Service
     Loaded: loaded (/etc/systemd/system/hypernets-sequence.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Thu 2021-02-04 05:28:33 CET; 4h 41min ago
    Process: 687 ExecStart=/home/gfz/Downloads/hypernets_tools/run_service.sh (code=exited, status=1/FAILURE)
   Main PID: 687 (code=exited, status=1/FAILURE)

Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: --> [Mode : vis | Action : bla | IT 0 ms] x 1 | total time : 0 ms]
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: --> [VNIR DARK 32768 65535] x 1
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: Spectrum #0 added
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: Saved to DATA/CUR20210204T042542/RADIOMETER/01_004_0000_0_0000_128_00_0000_01_0000.spe.
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: Last AIT-VNIR is now : 32768
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: Disabling Cooling...
Feb 04 05:28:31 gfz-pc1 run_service.sh[973]: DONE
Feb 04 05:28:33 gfz-pc1 run_service.sh[687]: Option : Keep PC ON
Feb 04 05:28:33 gfz-pc1 systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 05:28:33 gfz-pc1 systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.

Additionally, it is not pushing sequence to the server automatically!

Any advice?

We think that reorganizing the sequences folder by date would help the readability. After a couple of weeks, we have too many folders.
Moreover, within each sequence folder, all the sequence files have the same name. As an example, having downloaded a few images to understand where the instrument was pointing, all the jpeg are called 01_009_0270_2_0040.

Proper planning to ensure that sync of config_hypernets.ini between rugged PC and server does not led to system failure (e.g., if credentials are changed accidentally). This option is dangerous but very helpful (already used twice ;)). So I think it is nice to keep it but maybe there should be some fields that need to be write protected?

I am confused about this from the README.md instructions:

"If you are using Joel's script for binding instrument to /dev/radiometerX, you should be good, otherwise you should change in config_hypernets.ini the hypstar_port parameter to /dev/ttyUSBx (normally ttyUSB0)."

What is Joel's script? @jkuusk or @corizzi?

Thanks.

@vitbrando and I are still having this error:
error:ytcp:650:tcp(111):Connection refused

Example from the journalctl:

-- Boot 7d19d87261044c9d8ceefefc049dff0c --
mag 31 10:15:39 hypernets-cnr1 systemd[1]: Started Hypernets Sequence Service.
mag 31 10:15:39 hypernets-cnr1 run_service.sh[669]: Waiting for yoctopuce...
mag 31 10:15:41 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:42 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:44 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:45 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:47 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:48 hypernets-cnr1 run_service.sh[669]: .
mag 31 10:15:48 hypernets-cnr1 run_service.sh[669]: Ok !
mag 31 10:16:09 hypernets-cnr1 run_service.sh[855]: init error:ytcp:650:tcp(111):Connection refused
mag 31 10:16:09 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=1/FAILURE
mag 31 10:16:09 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.
-- Boot abf51ebb98d64b71880ea18054af2db1 --
mag 31 10:45:39 hypernets-cnr1 systemd[1]: Started Hypernets Sequence Service.
mag 31 10:45:39 hypernets-cnr1 run_service.sh[670]: Waiting for yoctopuce...
mag 31 10:45:41 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:42 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:44 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:45 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:47 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:48 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:50 hypernets-cnr1 run_service.sh[670]: .
mag 31 10:45:50 hypernets-cnr1 run_service.sh[670]: Ok !
mag 31 10:46:11 hypernets-cnr1 run_service.sh[860]: init error:ytcp:650:tcp(111):Connection refused
mag 31 10:46:11 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=1/FAILURE
mag 31 10:46:11 hypernets-cnr1 systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.
-- Boot 57073b994dfc47d9b9374780002438a3 --

Hi @corizzi ,

In logs, I have noticed that time begins as local time but the rest of the log uses UTC time!

-- Journal begins at **Mon 2022-03-14 15:59:27 GMT**, ends at Mon 2022-04-04 13:59:25 BST. --
Apr 04 13:25:13 gfz-pc systemd[1]: Started Hypernets Sequence Service.
Apr 04 13:25:14 gfz-pc run_service.sh[677]: [INFO]  Waiting for yoctopuce...
Apr 04 13:25:17 gfz-pc run_service.sh[677]: ..[INFO]  Ok !
Apr 04 13:25:17 gfz-pc run_service.sh[677]: [INFO]  Check Wake up reason...
Apr 04 13:25:18 gfz-pc run_service.sh[677]: [DEBUG]  Wake up reason is : schedule1.
Apr 04 13:25:18 gfz-pc run_service.sh[677]: [INFO]  Set relays #2 and #3 to ON.
Apr 04 13:25:18 gfz-pc run_service.sh[954]: INFO:root:[2, 3]
Apr 04 13:25:19 gfz-pc run_service.sh[961]: [INFO    2022-04-04T13:25:19] (open_sequence)
Apr 04 13:25:19 gfz-pc run_service.sh[961]: ---------------------------------------------------------------------
-----------

Hi! Having trouble after running the GUI and trying to make the connection.
This error stack is shown in the console:

[iafe1@iafe1-pc hypernets_tools]$ python -m hypernets.gui
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.9/tkinter/__init__.py", line 1892, in __call__
    return self.func(*args)
  File "/home/iafe1/hypernets_tools/hypernets/gui/frame_yoctopuce.py", line 30, in _connection
    self.connection()
  File "/home/iafe1/hypernets_tools/hypernets/gui/frame_yoctopuce.py", line 80, in connection
    states_relay = get_state_relay(-1)
  File "/home/iafe1/hypernets_tools/hypernets/scripts/relay_command.py", line 24, in get_state_relay
    relay_states.append(_alias_get_state(id_relay))
  File "/home/iafe1/hypernets_tools/hypernets/scripts/relay_command.py", line 18, in _alias_get_state
    return tuple((id_relay, relay.get_state()))
  File "/home/iafe1/.local/lib/python3.9/site-packages/yoctopuce/yocto_relay.py", line 137, in get_state
    if self.load(YAPI._yapiContext.GetCacheValidity()) != YAPI.SUCCESS:
  File "/home/iafe1/.local/lib/python3.9/site-packages/yoctopuce/yocto_api.py", line 5220, in load
    self._throw(res, errmsgRef.value)
  File "/home/iafe1/.local/lib/python3.9/site-packages/yoctopuce/yocto_api.py", line 4469, in _throw
    raise YAPI.YAPI_Exception(errType, "YoctoApi error : " + errorMessage)
yoctopuce.yocto_api.YAPI.YAPI_Exception: YoctoApi error : No function of that class (yapi:3811)

@corizzi Any idea what could be the reason for that? Thanks in advance!

Pablo

I am working remotely and after a while of being able to open the gui, now I am getting this error:

[hypernets@hypernets-cnr1 hypernets_tools]$ python -m hypernets.gui
init error:Unable to connect to server (ytcp:489)

Also, is there any way to reset or reboot the yoctopuse remotely?

On one occasion it took 17 minutes from the beginning of the sequence until instrument booted up. The cause was narrowed down to this line in run_service.sh

The supply current of the system increased ~50mA on 2021-02-06 08:30:04 (pan-tilt relay switched on) and increased again on 2021-02-06 08:47:00 (radiometer relay switched on).

@corizzi, All,

Sorry if I miss this information from another source, but I want to make sure I understand them correctly. What are the meanings or functionality of these parameters of the config file? What the best setting for the water unit on the field (@clemgoyens)?

[general]
keep_pc = on
start_sequence = yes
bypass_yocto = no

From #18, the keep_pc should be off, right?

PS: maybe, it could be useful to have some notes explaining the configuration file parameters. I could not find any.

Hi @corizzi,

As discussed yesterday, hereby a issue request to add header to the metadata. According to our mail from 14/12/2020 we agreed about the following headers:
[metada-header]
PI = Clém
site_name = Blankaart
SN_Hypstar = 120241
datetime = {datetime}
protocol = {protocol_file_name}
session = premier test en plein air

Could we also add:

Lat=43.69862
Lon=7.30692
Hypernets_tools_version = 000.125478

Thanks!!!
Clémence

Hi @corizzi,

I have updated my python to 3.10.1, Should I downgrade it or Hypernets_tools dependencies compatible with this version?

Tried merging your latest main branch into my fork, got following conflicts:

$ ./run_service.sh 
Bypassing Yocto
hypernets/resources/sequences_samples/sequence_kaspars.csv ${general:sequence_file}
usage: open_sequence.py [-h] -d -f FILE [--noyocto] [-p PORT]
                        [-l {ERROR,INFO,DEBUG,TRACE}] [-b BAUDRATE]
open_sequence.py: error: unrecognized arguments: ${general:sequence_file}
Hysptar scheduled job exited with code 2

config.ini in [metadata] section has "protocol_file_name = ${general:sequence_file}", which gets appended by awk to sequence_file.

Another issue was in read_protocol.py importing:
from hypernets.virtual.create_metadata import metadata_header
Assuming you meant "metadata_header_base", changed in code and got latest version executing.

Other than that prepare for pull request :)

Dear @corizzi and @stiebrs

We had used the call_radiometer.py script in the past to take a spectrum:
python -m hypernets.scripts.call_radiometer -rvnir -edark -v16

and use the accelerometer data to level the instrument. For instance, we had something like this:

python -m hypernets.reader -f DATA/20210409T153746.spe

Output :
Total Dataset Length : 4131
Spectrum Type Information : ('VIS', 'DARK')
Timestamp : 2021-04-09 15:37:47.048000
Exposure Time : 16
Temperature : 25.545764923095703
mean X : -15680
std X : 0
mean Y : -1600
std Y : 0
mean Z : -1856
std Z : 0

However, we could not find the call_radiometer.py script in the beta branch.

How could we have these parameters (X, Y, Z) using the beta branch?

When trying to measure using the gui, I am getting:

[hypernets@hypernets-cnr1 hypernets_tools]$ python -m hypernets.gui
29.18'C   23.6% RH   1011.66mbar   90.5lx
Position : 0°0'0"N 0°0'0"E
Datetime : N/A
offset_tilt : 60
offset_pan: 0
offset_tilt : 60
offset_pan: 0
VNIR Irradiance 8 0 1 0 2592 x 1944, 5MP
--> [1 2 8 0] x 1
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.8/tkinter/__init__.py", line 1883, in __call__
    return self.func(*args)
  File "/home/hypernets/hypernets_tools/hypernets/gui/frame_radiometer.py", line 155, in general_callback
    output = take_spectra(None, path.join(output_dir, output_name),
  File "/home/hypernets/hypernets_tools/hypernets/scripts/call_radiometer.py", line 123, in take_spectra
    instrument_instance = instanciation()
  File "/home/hypernets/hypernets_tools/hypernets/scripts/call_radiometer.py", line 37, in instanciation
    instrument_instance = Hypstar(instrument_port)
  File "/home/hypernets/hypernets_tools/hypernets/scripts/libhypstar/python/hypstar_wrapper.py", line 35, in __init__
    self.lib = CDLL('libhypstar.so')
  File "/usr/lib/python3.8/ctypes/__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/libstdc++.so.6)

I am not sure if it related to this, but when I am trying to reinstall 01_dependencies.sh:

[hypernets@hypernets-cnr1 install]$ ./01_dependencies.sh 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
warning: python-pip-20.3.1-1 is up to date -- reinstalling
warning: tk-8.6.11.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
 
Packages (2) python-pip-20.3.1-1  tk-8.6.11.1-1
 
Total Installed Size:  6,37 MiB
Net Upgrade Size:      0,00 MiB
 
:: Proceed with installation? [Y/n] Y
(2/2) checking keys in keyring                                       [######################################] 100%
(2/2) checking package integrity                                     [######################################] 100%
(2/2) loading package files                                          [######################################] 100%
(2/2) checking for file conflicts                                    [######################################] 100%
(2/2) checking available disk space                                  [######################################] 100%
:: Processing package changes...
(1/2) reinstalling python-pip                                        [######################################] 100%
(2/2) reinstalling tk                                                [######################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Traceback (most recent call last):
  File "/usr/bin/pip", line 33, in <module>
    sys.exit(load_entry_point('pip==20.3.1', 'console_scripts', 'pip')())
  File "/usr/bin/pip", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.8/importlib/metadata.py", line 504, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.8/importlib/metadata.py", line 177, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: pip

Small bug: in installation file with VOILA
When trying to move the P/T, the correct relay does not open! Solution: change the button to "open the correct PT relay" so that the user can choose the relay connected to the PT?
Maybe already fixed (can't test it anymore cause my instrument is on the field ;))

@corizzi

We tried to use the web dashboard:
[hypernets@hypernets-cnr1 utils]$ voila installation_on_site.ipynb --no-browser

, but it did not work with the following error:

ModuleNotFoundError: No module named 'hypernets.scripts'
ModuleNotFoundError: No module named 'hypernets.scripts'

I followed a set of instructions from #8 How to set up network, I tried to connect to NPL server and was not able to type the password when prompted and the leaving this empty did not work either.

[hypernets_npl@hypernetsnpl-pc hypernets_tools]$ sudo ./install/08_setup_server_communication.sh
[sudo] password for hypernets_npl:
Sorry, try again.
[sudo] password for hypernets_npl:
Sorry, try again.
[sudo] password for hypernets_npl:
sudo: 3 incorrect password attempts

When I change the wifi in Yoctowifi to Airplane mode as mentioned in here , I encounter this error when I try to connect in GUI:

init error: Unable to connect to server (ytcp:489)

this issue addressed #28; however, rebooting does not resolve the issue except it will turn on the Yoctowifi

Hello everyone,

I could not find an issue similar in this repo and I still do not have access to all the tickets in GLPI. Did anyone else face a similar error?:

We are testing the system inside my office. I am receiving the following error when running a sequence:

[hypernets@hypernets-cnr1 hypernets_tools]$ python -m hypernets.open_sequence -df hypernets/resources/sequences_samples/sequence_water_1_STD_1024.csv
== [Line 1] ============================================================
--> Requested Position (azimuth : 90.00 / sun ; zenith : 180.00)
Error : YoctoApi error : Device not found (yapi:3769)

However, the measurements and pictures are saved without problem.

Is this related to the not finding the gps issue?

Hi @corizzi - it would be really helpful in the hypernets processor to be able to tell when the data has finished transferring to the server, so we know when to begin processing. We originally opened an issue for this in hypernets_processor, where @jkuusk made a suggestion for a fix. Thanks!

@corizzi
When trying to take a picture with the GUI, there is an error: "3 is not a valid EntranceType". However, the picture is taken and saved in DATA.

At the end we took the picture using:
$ python -m hypernets.hypstar.handler -p

Hi Alex,

I have encountered this error
`FileNotFoundError: [Errno 2] No such file or directory: '/hypernets_tools/hypernets/resources/logo.png'
I noticed the logo.png is stored in img, but it calls it from resources.

I fixed it manually.

The stored jpg images contain lot of zeros in the end of the file (roughly half of the entire file). That doesn't corrupt the images, however, it wastes the disk space and network bandwidth when transferred to the server.

When trying to follow the following steps:
"Libhypstar driver is now bundled with installation, but needs to be activated and installed:

cd hypernets_tools
git submodule init
git submodule update
cd hypernets/scripts/libhypstar
make lib
sudo make install"

I am getting the following error:

[hypernets@hypernets-cnr1 libhypstar]$ make lib
-bash: make: command not found

Apparently there is no make to be found in the machine:

[hypernets@hypernets-cnr1 libhypstar]$ which make
which: no make in (/home/hypernets/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

After updating and installing libhypstar 0.2, the system is failing
The following error message when I ran run_service.sh

Bypassing Yocto
hypernets/resources/sequences_samples/sequence_land_STD_512.csv
SWIR:True, park:False
[INFO]	[2021-02-16T11:34:29] Creating serial port (baud=115200, portname=/dev/radiometer0)
/dev/radiometer0: No such file or directory

LibHypstar::linuxserial::linuxserial(int, const char*): serial port open failed.
[ERROR]	[2021-02-16T11:34:29] /dev/radiometer0 port open failed

[INFO]	[2021-02-16T11:34:29] Creating serial port (baud=115200, portname=/dev/radiometer0)
/dev/radiometer0: No such file or directory

LibHypstar::linuxserial::linuxserial(int, const char*): serial port open failed.
[ERROR]	[2021-02-16T11:34:29] /dev/radiometer0 port open failed

terminate called after throwing an instance of 'eHypstar'
run_service.sh: line 102:  1454 Aborted                 (core dumped) python3 -m hypernets.open_sequence -df $sequence_file $extra_args
Hysptar scheduled job exited with code 134

Any advice?

@clemgoyens, All,
For these instructions:

Wakeup Conditions :
Please refer to the Yoctopuce User Manual to set up Wakeup conditions for the system :
http://www.yoctopuce.com/EN/products/yoctohub-wireless/doc/YHUBWLN1.usermanual.html#CHAP9SEC1

I am confused about what we should set here. Is the daily waking up of the Yoctopuce? Or is the Waking up every 15 min for taking the measurement?

Thanks.

@corizzi

Last Wed we performed several test and we found the following issues and tired to guess the reason why.
Note: Just to inform, we are using another GPS outside the window so we now have date/time and position all the time.

• Yocto rebooting
  It seems that if it does not find internet connection in the first minute (?), it sends the SOS signal and reboots until internet connection is found. When the cable is connected there is no problem, but using 4G Sim card, connection is less stable or takes a bit longer to connect so it reboots until it finds the connection (last day it took 3 reboots to connect). Is there a way to set this "searching for internet" time a bit longer so it gives time for the PC to get a signal?

• Last week we made two complete series, one OK and one exiting with a failure (no error mentioned in the log). Both did the 17 lines of the sequence and had the recorded files correctly in the corresponding SEQ directories. The only difference was the PC KEEP ON/OFF option. Given that sequence is correctly saved, could it be possible that this failure in exit-code is not really an error?

-----------------------------------------------------------
ene 27 13:27:05 iafe1-pc run_service.sh[1571]: --> final pan : 349.9 ; final tilt : 0.18
ene 27 13:27:05 iafe1-pc run_service.sh[1571]: --> [Mode : non | Action : non | IT 0 ms] x 0 | total time : 0 ms]
ene 27 13:27:07 iafe1-pc run_service.sh[1174]: Option : Keep PC ON
ene 27 13:27:07 iafe1-pc systemd[1]: hypernets-sequence.service: Main process exited, code=exited, status=1/FAILURE
ene 27 13:27:07 iafe1-pc systemd[1]: hypernets-sequence.service: Failed with result 'exit-code'.
-------------------------------------------------
ene 27 15:13:29 iafe1-pc run_service.sh[1175]: --> final pan : 350.0 ; final tilt : 0.18
ene 27 15:13:29 iafe1-pc run_service.sh[1175]: --> [Mode : non | Action : non | IT 0 ms] x 0 | total time : 0 ms]
ene 27 15:13:32 iafe1-pc run_service.sh[934]: Option : Keep PC OFF
ene 27 15:13:32 iafe1-pc systemd[1]: hypernets-sequence.service: Succeeded.

• We also had unexpected re-bootting of the system in the middle of a sequence without any clear reason.

Any news from Yocto or updates are very welcome so we can continue testing next Wednesday at the lab.
Thanks

Ana

It seems that the sequence folder name is writing the local time, instead of the UTC time.
Maybe this line:

To Reproduce:

1. capture whatever spectrum
2. view graph
3. close graph
4. try opening graph again
5. If that works, try clicking next/previous