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
We have some tests running in the CI, but since atom mapping could have so many corner cases I think it's valuable that we expand the tests for the atom mapper to more of these. This issue is intended at discussing which cases are desired to be tested. As far as I can think of, we would like to have at least the following tests that are related to protein/residue mutations.
Different capped AAs mapping. Some "key" cases and check that the mapped atoms are the expected ones.
Full protein mappings. Maybe a tyk2 with a mutated tyk2 or similar.
Mapping of proteins (or big molecules) on itself, we would expect every atom to be mapped.
Mapping big protein to small peptides/AAs or vice versa.
As usual more than coverage we want more test cases, so I think this is something somewhat desired. One caveat is that some of these tests could take a few minutes to make the whole mapping. But this could also be helpful to do benchmarking on our current implementation.
The text was updated successfully, but these errors were encountered:
Just wanted to note that we are including some tests for multimeric protein component mappings in #47 , but while working on that I realize that we probably also want to have more tests at different levels.
We have some tests running in the CI, but since atom mapping could have so many corner cases I think it's valuable that we expand the tests for the atom mapper to more of these. This issue is intended at discussing which cases are desired to be tested. As far as I can think of, we would like to have at least the following tests that are related to protein/residue mutations.
As usual more than coverage we want more test cases, so I think this is something somewhat desired. One caveat is that some of these tests could take a few minutes to make the whole mapping. But this could also be helpful to do benchmarking on our current implementation.
The text was updated successfully, but these errors were encountered: