baidu / baidu/DuReader

Five questions have arisen when i run "sh run.sh --train --pass_num 5 --use_gpu=False".

Open
#59 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1.2k
Forks
306
PR merge metrics
No merged PRs in 30d

Description

1)ParallelExeccutor is deprecated.Please use CompiledProgram and Executor.CompiledProgram is a central place for optimization and Executor is the unified executor.Example can be found in conpiler.py.

2)[3548 graph.h:204]WARN:After a series of passes,the current graph can be quite different from OriginProgram.So,pleasse avoid using the ' OriginProgram () 'method!

3)You can try our memory optimize feature to save your memory usage:...
![image](https://user-images.githubusercontent.com/49556768/58633822-42875880-831c-11e9-9fc0-c3fba6b45037.png)

4)The number of graph should be only one,but the current graph has 8 sub_graphs.If you want to see the nodes of the sub_graphs,you should use 'FLAGS_print_sub_graph_dir' to specify the output dir. NOTES : if you not do training,please don't pass loss_var_name.

5)Traceback (most recent call last):
File "run.py",line 645, in
train(logger, args)
File "run.py", line 464, in train
args)
File "run.py", line 308, in validation
ave_loss = 1.0 * total_loss / count
ZeroDivisionError: float division by zero

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the command `sh run.sh --train --pass_num 5 --use_gpu=False` and inspect `run.py`, especially `train` at line 464 and `validation` at line 308. Determine why validation reaches the reported ZeroDivisionError and separately verify whether the four compiler and graph messages are expected; done means the training command completes without the reported failure and the resulting behavior is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.