Bogus mutation: "* 1." -> "/ 1."
See original GitHub issueExample:
- Z_available = molinit['elez'] * molinit['real'] * 1.
+ Z_available = molinit['elez'] * molinit['real'] / 1.
mutmut version 1.5.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Identification of false-negative mutations missed by next ...
In brief, we support the need for a complementary approach to identify mutations undetected by NGS, underscoring the power and significance ...
Read more >Genetic Mutation | Learn Science at Scitable - Nature
For mutations to affect an organism's descendants, they must: 1) occur in cells that produce the next generation, and 2) affect the hereditary...
Read more >The rate and spectrum of mosaic mutations during ...
This novel approach permitted us to (1) reliably distinguish somatic mutations from germline variants and post-transcriptional modifications, (2) ...
Read more >Definition of false-positive result - NCI Dictionary of Genetics ...
A test result that indicates an individual is affected and/or has a certain gene mutation when he or she is actually unaffected and/or...
Read more >False-negative errors in next-generation sequencing ... - PLOS
(2019) False-negative errors in next-generation sequencing contribute substantially to inconsistency of mutation databases. PLoS ONE 14(9): ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the quick response!
The problem is that this mutation causes a false positive for every standard type. For numeric types – I tested int, float, bool and corresponding numpy types –
* 1.
and/ 1.
give the same result (e.g.42 * 1. == 42 / 1.
). For other types – I tested list, set, str, dict, and None — both* 1.
and/ 1.
cause a TypeError.Cool! Always happy to hear people are using mutmut. Hope it goes well and I’d love to hear any more feedback you might have.