You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have written a simple program using LDPC that runs on an Ubuntu 22.04 embedded system with dual Cortex A9 cores. I need the program to run automatically, so I created a systemd service so that it would start at boot. Unfortunately, when starting this way, I get the following error:
terminate called after throwing an instance of 'aff3ct::tools::invalid_argument'
what(): In the '/home/xilinx/aff3ct/aff3ct/src/Tools/Code/LDPC/Matrix_handler/LDPC_matrix_handler.cpp' file at line 63 ('read' function): "'filename' couldn't be opened ('filename' = matrixes/MACKAY_504_1008.alist)."
When I run the program form the command line, I do not get this error, and the program runs fine.
I have verified that he directory and file (matrixes/MACKAY_504_1008.alist) have the read permissions set (all have read access).
Any help on this matter would be appreciated.
The text was updated successfully, but these errors were encountered:
I have written a simple program using LDPC that runs on an Ubuntu 22.04 embedded system with dual Cortex A9 cores. I need the program to run automatically, so I created a systemd service so that it would start at boot. Unfortunately, when starting this way, I get the following error:
terminate called after throwing an instance of 'aff3ct::tools::invalid_argument'
what(): In the '/home/xilinx/aff3ct/aff3ct/src/Tools/Code/LDPC/Matrix_handler/LDPC_matrix_handler.cpp' file at line 63 ('read' function): "'filename' couldn't be opened ('filename' = matrixes/MACKAY_504_1008.alist)."
When I run the program form the command line, I do not get this error, and the program runs fine.
I have verified that he directory and file (matrixes/MACKAY_504_1008.alist) have the read permissions set (all have read access).
Any help on this matter would be appreciated.
The text was updated successfully, but these errors were encountered: