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

stage11 stage13 issues #15

Open
Wujianting opened this issue May 6, 2022 · 9 comments
Open

stage11 stage13 issues #15

Wujianting opened this issue May 6, 2022 · 9 comments

Comments

@Wujianting
Copy link

Wujianting commented May 6, 2022

Hello, I have some problems need your help me.
In stage 11:
11
////////////////////////////////////////////////////////////////////////////////////
In stage 13:
22

Can you help me?
Thank you

@Wujianting Wujianting changed the title stage12 stage13 issues stage11 stage13 issues May 6, 2022
@Natalia-T
Copy link
Collaborator

Hi @Wujianting,
For the first problem:

You can try to add to env.sh:
export PYTHONPATH=<your path>/anonymization_metrics:$PYTHONPATH

This is done in

PYTHONPATH=$(realpath ../anonymization_metrics) python local/scoring/linkability/compute_linkability.py \

Ideally, this should be in env.sh

@Natalia-T
Copy link
Collaborator

For the second problem, could you please attach the corresponding logs rescorelm.*.log?

@Wujianting
Copy link
Author

@Wujianting
Copy link
Author

Hi @Wujianting, For the first problem:

You can try to add to env.sh: export PYTHONPATH=<your path>/anonymization_metrics:$PYTHONPATH

This is done in

PYTHONPATH=$(realpath ../anonymization_metrics) python local/scoring/linkability/compute_linkability.py \

Ideally, this should be in env.sh

I have successfully solved the problem of stage11. Thank you for your help.
Solution: I used git clone to download anonymization again_ metrics.
But I still haven't solved stage13. Please help me solve it in your spare time. Thank you very much.

@Natalia-T
Copy link
Collaborator

For the second problem, some of the processes were killed by the system as written in the logs, i.e., in rescorelm.1.log: 31838 Killed

@Wujianting
Copy link
Author

对于第二个,一些被系统处理的问题,如日志中所写,rescorelm.1.log 31838 Killed

Hello, let me make it clear that the second screenshot is the result of running stage13 only. Is there a necessary process for stage13 in the previous stage?
Do you mean that the whole process of stage 1-16 can not run continuously?

@Natalia-T
Copy link
Collaborator

To run Stage 13, Stage 12 (Make ASR evaluation subsets) should be completed; Stage 11 is not necessary for that.

In Stage 13, most of your 16 processes correctly worked, and some of them were killed by another process/service in your system. I can not say which service in your system and why killed some of the processes at Stage 13. Where did you run your scripts - on the cluster or work station?

@Wujianting
Copy link
Author

Wujianting commented May 8, 2022

要运行Stage 13Stage 12(制作 ASR 评估子集)应该完成;Stage 11没有必要这样做。

Stage 13中,您的 16 个进程中的大多数都正常工作,其中一些被系统中的另一个进程/服务杀死。我不能说你系统中的哪个服务以及为什么杀死了一些进程Stage 13。您在哪里运行脚本 - 在集群或工作站上?

I connect wsl2 through visual studio code on my computer to experiment.
This is my whole process, Please have a look. Thank you very much.
XAA{@V7ANYW9H9G$WKWA8

@Natalia-T
Copy link
Collaborator

What happens with the processes in wsl2 if the memory exceeds the available capacity? Would it kill the processes?
You can try to run decoding (and LM scoring) in 1 thread instead of 16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants