Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] data was not collected with "context_type=local" #379

Open
Weizhang88 opened this issue Jun 17, 2023 · 3 comments
Open

[BUG] data was not collected with "context_type=local" #379

Weizhang88 opened this issue Jun 17, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@Weizhang88
Copy link

Summary
Output data was not collected from the temporary folder.
I was using dpgen to do some autotest work with my local computer. The context_type=local in the machine.json file. After successfully calculation, the oupt files were not collected back to the original input file contained dir.
context_type=lazylocal is working.

"batch_type": "shell", "context_type": "local", "local_root": "./", "remote_root": "xyz"

DPGEN Version and Platform
0.11.1 local computer

Job submission and computing cluster configuration

Expected Behavior

Actual Behavior

Steps to Reproduce

Further Information, Files, and Links

@Weizhang88 Weizhang88 added the bug Something isn't working label Jun 17, 2023
@njzjz
Copy link
Member

njzjz commented Jun 22, 2023

Hi @Weizhang88, what task did you run? What file should be collected?

@Weizhang88
Copy link
Author

Weizhang88 commented Jun 27, 2023

Hi @Weizhang88, what task did you run? What file should be collected?

Sorry for the late reply. I just used dpgen run para.json machine.json to collect data sets for training on my own local computer.

Recently, I upgraded dpgen from version 0.10.6 to version 0.11.1 and made changes to the machine.json file to accommodate the new version. When I specified "context_type": "local" like before, a temporary directory was created where the calculations were processed. However, after the calculations were completed, the temporary directory was deleted and the output files (e.g. output from cp2k) were not collected backward to the original directory within the iter.000000 directory (as an example).

'context_type=lazylocal' is working and does not create a temporary directory. dp or lmp were executed in the original directory. However, when I stopped the dpgen run with ctrl + c using this setting, the dp, lmp, or cp2k processes were still running in the terminal shell. I had to use the command kill $(pgrep cp2k) to terminate them. This behavior was not observed with "context_type": "local", as the dp or lmp processes were terminated simultaneously with the dpgen run using ctrl + c.

Therefore, I prefer to use "context_type": "local" as it allows for easier control of the process.

@njzjz njzjz transferred this issue from deepmodeling/dpgen Oct 16, 2023
@njzjz
Copy link
Member

njzjz commented Oct 16, 2023

Do you use the latest dpdispatcher? Could you provide the structure of directories?

I checked LocalContext and LazyLocalContext. The codes to execute commands are the same, so there should be no difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants