mapping beteween loc_index and global_index

I noticed that there is an output parameter N_loc in the construct_init function. I'd like to understand the purpose of this parameter. Does this parameter correspond to each process's local index range (1:N_loc, 1:N_loc)? And can we use the msh%new2old() interface to obtain the global indices, which would correspond to the index range of elements that each process needs to retrieve through the element computation function during the compression process?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information