From 6189adbbb0f04dd446c98821246d0f259d8e5e4d Mon Sep 17 00:00:00 2001 From: vladislav doster Date: Mon, 23 Dec 2024 13:47:27 -0600 Subject: [PATCH] docs: fix typo in ConfiguringInfinigen.md `paralell` ==> `parallel` --- docs/ConfiguringInfinigen.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ConfiguringInfinigen.md b/docs/ConfiguringInfinigen.md index 6c46618f..817968eb 100644 --- a/docs/ConfiguringInfinigen.md +++ b/docs/ConfiguringInfinigen.md @@ -27,7 +27,7 @@ Typically, these tasks are as follows: The outputs for all tasks belonging to a particular scene will be stored in the `outputs/MYJOB/SEED`, where MYJOB was the folder name chosen in the `--output_folder` argument, and `SEED` is the random seed used to create the scene. Each task creates its own detailed log files in `outputs/MYJOB/SEED/logs/TASKNAME.log` and `outputs/MYJOB/SEED/logs/TASKNAME.err` - please check these logs to see detailed error messages if your jobs crash . -Infinigen is designed to run many independent scenes in paralell. This means that even if running all the steps for each scene can take some time, we can still achieve good throughput and utilization (provided it has enough resources - most laptops only have enough RAM for one scene at a time). +Infinigen is designed to run many independent scenes in parallel. This means that even if running all the steps for each scene can take some time, we can still achieve good throughput and utilization (provided it has enough resources - most laptops only have enough RAM for one scene at a time). #### Overrides and Config Files