nemo_rl
#
Subpackages#
nemo_rl.utils
nemo_rl.experience
nemo_rl.environments
nemo_rl.data
nemo_rl.data.eval_datasets
nemo_rl.data.hf_datasets
nemo_rl.data.hf_datasets.chat_templates
nemo_rl.data.hf_datasets.openmathinstruct2
nemo_rl.data.hf_datasets.helpsteer3
nemo_rl.data.hf_datasets.squad
nemo_rl.data.hf_datasets.prompt_response_dataset
nemo_rl.data.hf_datasets.dpo
nemo_rl.data.hf_datasets.deepscaler
nemo_rl.data.hf_datasets.oasst
nemo_rl.data.hf_datasets.oai_format_dataset
nemo_rl.data.packing
nemo_rl.data.datasets
nemo_rl.data.interfaces
nemo_rl.data.llm_message_utils
nemo_rl.data.processors
nemo_rl.distributed
nemo_rl.algorithms
nemo_rl.converters
nemo_rl.models
nemo_rl.metrics
nemo_rl.evals
Submodules#
Package Contents#
Functions#
Patch the nsight.py file to fix the context.py_executable assignment. |
Data#
API#
- nemo_rl.megatron_path#
None
- nemo_rl._patch_nsight_file()[source]#
Patch the nsight.py file to fix the context.py_executable assignment.
Until this fix is upstreamed, we will maintain this patch here. This patching logic is only applied if the user intends to use nsys profiling which they enable with NRL_NSYS_WORKER_PATTERNS.
If enabled, will effectively apply the following patch in an idempotent manner:
https://github.com/ray-project/ray/compare/master…terrykong:ray:tk/nsight-py-exeutable-fix?expand=1
This hack works b/c the nsight plugin is not called from the main driver process, so as soon as nemo_rl is imported, the patch is applied and the source of the nsight.py module is up to date before the nsight.py is actually needed.