2021-06-28 13:48:01.293305: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'libcudart.so.10.1'; dlerror: libcudart.so.10.1: cannot open shared object file: No such file or directory
2021-06-28 13:48:01.293338: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
tensorflow version 2.3.3
Traceback (most recent call last):
File "/home/richel/.local/share/gcaer/gcae_v1_0/run_gcae.py", line 396, in <module>
with open("data_opts/" + data_opts_id+".json") as data_opts_def_file:
FileNotFoundError: [Errno 2] No such file or directory: 'data_opts/b_0_4.json'
The drawback is that this is too long of an error message for R to display (here I use the gcaer R package):
Also, one could argue that initializing Tensorflow and looking for CUDA should be done after checking if the CLI arguments are valid.
In that way, the error message would shorten to the lines below and I would be happy:
Traceback (most recent call last):
File "/home/richel/.local/share/gcaer/gcae_v1_0/run_gcae.py", line 396, in <module>
with open("data_opts/" + data_opts_id+".json") as data_opts_def_file:
FileNotFoundError: [Errno 2] No such file or directory: 'data_opts/b_0_4.json'
An alternative would be to be able to remove these Tensorflow warnings from a CLI argument.
What I suggest is one of these options:
Load Tensorflow after checking the CLI arguments
Add the ubiquitous --verbose argument and only show the Tensorflow things when it is enabled
Dear GCAE maintainer,
Here I try to convince you to give a shorter error message when
--datadir
is absent.Thanks for the GCAE examples provided; these are very helpful!
When I run the example code of the first GCAE training example ...
I get a clear-but-long error message:
The drawback is that this is too long of an error message for R to display (here I use the gcaer R package):
Also, one could argue that initializing Tensorflow and looking for CUDA should be done after checking if the CLI arguments are valid.
In that way, the error message would shorten to the lines below and I would be happy:
An alternative would be to be able to remove these Tensorflow warnings from a CLI argument.
What I suggest is one of these options:
--verbose
argument and only show the Tensorflow things when it is enabledWhat do you think about this idea?