Hi Alex
You can use db_xref. However Artemis should recognise hyperlinks in any
qualifier e.g. /note.
Cheers
Tim
On 4/12/12 9:15 PM, Bossers, Alex alex.boss...@wur.nl wrote:
Tim,
which FeaTure key would be best to use when wanting hyperlinked db refs? Is
there some convention?
Hi Alex
No that isn't the intended behaviour. This view is still in development so
thank you for the feedback. I have changed the code so that all frame line
features (not just CDS features) should now be separated out. So you should
hopefully then see your 4 BLASTCDS features. This is now
Tim,
which FeaTure key would be best to use when wanting hyperlinked db refs? Is
there some convention?
/db_xref=GI:somenumber?
Alex
Van: Bossers, Alex
Verzonden: woensdag 11 april 2012 22:31
To: Tim Carver; artemis-users@sanger.ac.uk
Onderwerp: RE:
Hi
I am playing around again with multiple annotation tracks in Artemis latest
version locally...
I managed to get BLAST results in the annotation as well as other EMBL FT.
I wondered is it possible to get for let's say a limited BLAST to 4 matches
each entry, to display all those 4 as
Hi Alex
I am not sure of the best way to limit the number of hits to an ORF but you
may be interested in a new view which is in development at the moment in
Artemis. It displays overlapped features in a 'Feature Stack View'.
Currently this is in the development version of Artemis,
Tim,
thanks for the rapid reply!
I will have a look at the dev version. Sounds interesting.
Regarding the blast tracks. What I do is I generate ORFs using gmHMM or
prodigal... and blast those in one go limiting 4 hits each. I than postprocess
these files into embl annotation files using the ORF
