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

Converting megatron checkpoint to .nemo without the same environment #9516

Closed
dachenlian opened this issue Jun 21, 2024 · 3 comments
Closed
Assignees
Labels

Comments

@dachenlian
Copy link

I have multiple checkpoints produced after running examples/nlp/language_modeling/megatron_gpt_continue_training.py.

However, I am unable to use examples/nlp/language_modeling/megatron_ckpt_to_nemo.py to convert it to a .nemo object. It's probably because the environment in which I want to do the conversion is the not the same as the one used for training. Is there some way to do the conversion only on CPU or just 1 GPU?

I have tried using two different sets of parameters:


Input:

srun -p ${PARTITION} -G 1 \
    --container-image /mnt/nemo_dev.sqsh \
    --container-mounts ${LAUNCHER_SCRIPT_PATH}:${LAUNCHER_SCRIPT_PATH},${NEMO_PATH}:${NEMO_PATH} \
    --container-writable \
    --no-container-mount-home \
    --pty bash -c \
    "python ${NEMO_PATH}/examples/nlp/language_modeling/megatron_ckpt_to_nemo.py --checkpoint_folder ${CKPT_FOLDER} --checkpoint_name ${CKPT_NAME} --nemo_file_path ${NEMO_FILE_PATH} --model_type gpt --gpus_per_node 1 --tensor_model_parallel_size 1 --pipeline_model_parallel_size 1 --precision bf16-mixed"

Output:

megatron_ckpt_to_nemo.py 243 <module>                                                                                                                                     
convert(local_rank, rank, world_size, args)                                                                                                                               

megatron_ckpt_to_nemo.py 196 convert
model = MegatronGPTModel.load_from_checkpoint(checkpoint_path, hparams_file=args.hparams_file, trainer=trainer)

nlp_model.py 397 load_from_checkpoint
checkpoint = dist_checkpointing.load(sharded_state_dict=checkpoint, checkpoint_dir=checkpoint_dir)

serialization.py 131 load
validate_sharding_integrity(nested_values(sharded_state_dict))

serialization.py 404 validate_sharding_integrity
_validate_sharding_for_key(shardings)

serialization.py 442 _validate_sharding_for_key
raise CheckpointingException(f'Invalid access pattern for {rank_sharding[0][1]}')

megatron.core.dist_checkpointing.core.CheckpointingException:
Invalid access pattern for ShardedTensor(key='model.embedding.word_embeddings.weight')

Input:

srun -p ${PARTITION} -G 1 \
    --container-image /mnt/nemo_dev.sqsh \
    --container-mounts ${LAUNCHER_SCRIPT_PATH}:${LAUNCHER_SCRIPT_PATH},${NEMO_PATH}:${NEMO_PATH} \
    --container-writable \
    --no-container-mount-home \
    --pty bash -c \
    "python ${NEMO_PATH}/examples/nlp/language_modeling/megatron_ckpt_to_nemo.py --checkpoint_folder ${CKPT_FOLDER} --checkpoint_name ${CKPT_NAME} --nemo_file_path ${NEMO_FILE_PATH} --model_type gpt --gpus_per_node 8 --tensor_model_parallel_size 2 --pipeline_model_parallel_size 1 --precision bf16-mixed"

Output:

megatron_ckpt_to_nemo.py 243 <module>
convert(local_rank, rank, world_size, args)

megatron_ckpt_to_nemo.py 153 convert
trainer = Trainer(plugins=plugins, strategy=strategy, **cfg.trainer)

argparse.py 70 insert_env_defaults
return fn(self, **kwargs)

trainer.py 401 __init__
self._accelerator_connector = _AcceleratorConnector(

accelerator_connector.py 149 __init__
self._check_device_config_and_set_final_flags(devices=devices, num_nodes=num_nodes)

accelerator_connector.py 325 _check_device_config_and_set_final_flags
raise ValueError(f"`num_nodes` must be a positive integer, but got {num_nodes}.")

ValueError:
`num_nodes` must be a positive integer, but got 0.
@dimapihtar
Copy link
Collaborator

Hi @dachenlian,
Could you try to specify --hparams_yaml param? You can find hparams.yaml file in train results folder. It should be in "version_0" or "run_0" folder.

Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Aug 18, 2024
Copy link
Contributor

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants