Thank you for sharing your experience. I used vg gbwt -M -C -H -S -L -T joint-full.cov.gbwt to view the information in the gbwt index, which is as follows:
29379 paths with names, 12 samples with names, 12 haplotypes, 10 contigs with names
Chr1
Chr3
Chr2
Chr10
Chr7
Chr9
Chr6
Chr8
Chr4
Chr5
12
COR_A
COR_B
COR_C
COR_D
COR_E
COR_F
COR_G
COR_H
COR_I
COR_J
COR_K
COR_L
_thread_COR_A_Chr10_0_0
_thread_COR_B_Chr10_0_107698
_thread_COR_B_Chr10_0_198532
_thread_COR_B_Chr10_0_291916
_thread_COR_B_Chr10_0_759772
_thread_COR_B_Chr10_0_943427
_thread_COR_B_Chr10_0_1088850
_thread_COR_B_Chr10_0_1166426
_thread_COR_B_Chr10_0_1229383
_thread_COR_B_Chr10_0_1992992
_thread_COR_B_Chr10_0_2266779
_thread_COR_B_Chr10_0_2317201
_thread_COR_B_Chr10_0_2361082
_thread_COR_B_Chr10_0_2377269
_thread_COR_B_Chr10_0_2521740
_thread_COR_B_Chr10_0_2552854
...
The names of thread shown here are completely different from those in the gfa P line path, which confuses me as to how to make the chromosome paths match. Even if I modify the chromosome name of the gff file according to the above thread name, it still doesn't work.