Fix a bug in CTM line processing function for multi-speaker data simulations

[tango4j]

What does this PR do ?

This PR fixes the bug in scripts/speaker_tasks/create_alignment_manifest.py.
The get_seg_info_from_ctm_line function was outputing values in a wrong order.
Plus, confidence value could be set to None to prevent any type error issues.

Collection:
ASR (Multi-speaker Data Simulation, CTM annotation generation part)

Changelog

• the output variable orders in get_seg_info_from_ctm_line function.
• conf=0 to conf=None

Usage

• You can potentially add a usage example below

python scripts/speaker_tasks/create_alignment_manifest.py \                                                                                                                                                
  --input_manifest_filepath LibriSpeech/dev_clean.json \                                                                                                                                                         
  --base_alignment_path LibriSpeech_Alignments \                                                                                                                                                                 
  --output_manifest_filepath ./dev-clean-align.json \                                                                                                                                                            
  --ctm_output_directory ./ctm_out \                                                                                                                                                                             
  --libri_dataset_split dev-clean          

Jenkins CI

To run Jenkins, a NeMo User with write access must comment jenkins on the PR.

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in ASR can review this.

Additional Information

• Related to # (issue)

[nithinraok]

LGTM

[nithinraok]

Jenkins