You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working to add support for the basemod API to rust-htslib (rust-bio/rust-htslib#385) and am a bit confused about the base_mod_query_type function. I currently use it to retrieve metadata (strand, canonical base, implicit/explicit flag) for each modification code but when writing a test around MM-double.sam I realized that it will always return metadata for the first m mod (C+m, never G-m) in the record. Is it intended that user-level code uses base_mod_query_type, or should we only use the data returned during iteration (like in the test_mod.c driver code)?
The text was updated successfully, but these errors were encountered:
@cjw85 just pointed out to me this is essentially the same as #1550. Feel free to close to keep the discussion in one place but it might be good to add a new API call base_mod_queryi (or something) that returns metadata for the i-th modification in the record, to be used with bam_mods_recorded.
I've been working to add support for the basemod API to rust-htslib (rust-bio/rust-htslib#385) and am a bit confused about the
base_mod_query_type
function. I currently use it to retrieve metadata (strand, canonical base, implicit/explicit flag) for each modification code but when writing a test around MM-double.sam I realized that it will always return metadata for the firstm
mod (C+m
, neverG-m
) in the record. Is it intended that user-level code usesbase_mod_query_type
, or should we only use the data returned during iteration (like in the test_mod.c driver code)?The text was updated successfully, but these errors were encountered: