I am using smartdispatch to launch commands that happen to be prefixed by things like "export VAR=...".
In SMART_DISPATCH_LOGS, I end up with directory names that are completely informative, and whose sole differentiating factor is the timestamp at the beginning of the file.
Now, one option is to just forget about this and add the "export" commands to my .bashrc, so that names will not get cut off. This is what I'll do for now. But it would be nice to be able to specify my own name for jobs. The timestamp prefix can still be added, but I'll be able to provide an informative name for the jobs instead of having a directory full of names like the above.
(I spoke with Mathieu about this and he recommended that I create an issue just to keep track of it. This is not an urgent issue for me in any way.)
I am using smartdispatch to launch commands that happen to be prefixed by things like "export VAR=...".
In SMART_DISPATCH_LOGS, I end up with directory names that are completely informative, and whose sole differentiating factor is the timestamp at the beginning of the file.
2016-09-14_13-09-57_pythonpathsoftware6appsmercurial272lib64python26site_packageshomealainguideep_learning_suitetensorflow_modelsinception_ld_library_pathsoftware_gpulibscudnn5_cuda75lib64homealainguilocallib64homealainguilocallibhomeaNow, one option is to just forget about this and add the "export" commands to my .bashrc, so that names will not get cut off. This is what I'll do for now. But it would be nice to be able to specify my own name for jobs. The timestamp prefix can still be added, but I'll be able to provide an informative name for the jobs instead of having a directory full of names like the above.
(I spoke with Mathieu about this and he recommended that I create an issue just to keep track of it. This is not an urgent issue for me in any way.)