Feature #1702
closedExtract error trace parser from error-trace-visualizer
0%
Description
This task becomes actual because of rather close connection between KB scripts and error trace parser (see blocked issues).
Updated by Evgeny Novikov almost 13 years ago
- Priority changed from Normal to High
Raise this bug priority as it represents a part of #1637 issue having to be done.
Updated by Pavel Shved almost 13 years ago
There are more things to decouple from the error trace visualizer. One of them, about which we completely forgot, is that a verifier's developer should specify an error trace converter!
This bring us back to the discussion on what should be treated as an error trace, and what centralized format should be supported. But, surely, the parser that transforms BLAST's error trace to in-memory Perl data structures (I guess, that's what you meant) should be decoupled.
Updated by Evgeny Novikov almost 13 years ago
It seems that error trace visualizer should be redesign at last :)
Updated by Evgeny Novikov almost 13 years ago
- Status changed from Open to Resolved
Initially desired feature was resolved in 9c4ac3f of knowledge-base-2 branch. Other efforts of error trace visualizer redesign, in particular to clarify the way of a new verifier error trace support, should be considered in other places.
Updated by Evgeny Novikov almost 13 years ago
- Status changed from Resolved to Closed
It's in master now. Nevertheless in redesigning of ETV this also should be taken into account.
Updated by Evgeny Novikov almost 13 years ago
- Published in build changed from 6fd6348 to 9c4ac3f