-
Notifications
You must be signed in to change notification settings - Fork 1.8k
when searchspace type set loguniform, could the _value min not set too small? #4195
Comments
I found this maybe because I run this expriment on dorcker. I later run it well on a real machine . |
Would you like to share us the version of docker image? I will try it in docker ASAP. |
docker will not be shared because it is not pulled common docker hub. |
Thank you. And I wonder if you run the experiment with a config file like '*.yaml'? If you do, please share me a copy with that : ) |
config.yml , as below:
|
I ran the experiment in docker with almost the same environment( |
thank you very much, I will check the log as you say. if I find some reason, I will exchange the message with u. |
I think about a way of trying to cheat that crontab a task "ps -aux|grep -v grep|grep defunct |awk '{print $2}'|xargs -n1 -I {} kill -s 9 {}". when this zombie pid appear,kill it because I think these zombie pid appear so that nni regard as this zombie task run continue. |
Did you notice the time stamp between |
in dispatcher.log and nnimanager.log,I didn't find the words "terminated" and "task stopped". my nni version is 2.4 . |
It may crush while processing. A possible solution is to use |
I could show some key log, the duplicate log will be replaced with "..." .because the log is too long. [nnimanager.log]
[dispatcher.log]
|
The sentences are from |
I understand the early_stopped policy.my meaning of before description "INFO (NNIManager) Trial job OJlVS status changed from WAITING to RUNNING" is that the task of OJlVS log in nnimanager.log only show state is RUNING ,not SUCCEED or EARLY_STOPPED if run right. |
Describe the issue:
I have an expriment run some time,expriment could stop
I find that when the expriment stops, after ps -aux , COMMAND col appear some "[bash] < defunct >",Parent process don't deal with this Zombie process?
or
search space i use {"_type":"loguniform","_value":[0.000001,0.001]}
Is it that _value min value too small when numerical calculation log, log go wrong ?(i guss too small _value will regard as 0?)
when I set _type to uniform; expriment run normally.
Environment:
How to reproduce it?:
The text was updated successfully, but these errors were encountered: