Search results
From irefindex
Create the page "Search" on this wiki! See also the search results found.
- ...h]]), index ([[Using the Bioscape Web Application#Advanced_Search|advanced search]])3 KB (403 words) - 13:47, 14 July 2010
- ...e-grained tokenisation policy on any text thought to contain mentions of a search term, then validating such possible mentions using the more precise tokens. ...is strategy is the effect of discarding tokens from search terms: should a search term be rendered ambiguous or even eliminated by token filtering, such term6 KB (954 words) - 13:45, 14 July 2010
- ==Search tools== This sub menu contain search related operations.2 KB (335 words) - 15:01, 28 June 2011
- ** [[Displaying Bioscape Search Results]]827 bytes (77 words) - 13:36, 14 July 2010
- ...n Source Text Mining Tools for Cancer Surveillance] [http://209.85.129.132/search?q=cache:IdtRfrugXh0J:www.cdc.gov/cancer/npcr/npcrpdfs/text_mining_tools.pdf === Text Search Resources ===9 KB (1,355 words) - 14:04, 17 February 2010
- http://wodaklab.org/iRefWeb/search/index?q=xxx:yyy You can also use this xxx:yyy format directly in the iRefWeb search interface for advanced searching or to test links to iRefWeb.3 KB (522 words) - 01:14, 5 August 2010
- # Search biomedical literature using the contents of the lexicon, subject to filteri # Assign bioentities to the text search results.13 KB (1,932 words) - 13:43, 14 July 2010
- ==Search cases== Search type: UniProt_Ac20 KB (3,064 words) - 12:43, 15 June 2010
- ==Search tools== ...'''selected nodes'''. This action is the same as performing a iteration=1 search using iRefScape for the selected nodes.9 KB (1,459 words) - 15:45, 6 July 2011
- === Search for interactions involving “QCR2_HUMAN”=== # Select "Search protein-protein interactions for a protein".19 KB (3,075 words) - 16:29, 6 July 2011
- ==Using the Wizard - an example search == # Select "Search protein-protein interactions for a protein".25 KB (4,001 words) - 16:28, 6 July 2011
- Bioscape combines a number of processes in order to produce search results from textual document and other data. This document attempts to des ...gin, the documents to be searched must be acquired and processed such that search operations performed on these documents may be done relatively efficiently.24 KB (3,501 words) - 13:46, 14 July 2010
- directed, 641 nodes , 1586 Edges, (search results for Raf1, type=geneSymbol, taxid=any from iRefsCape )2 KB (243 words) - 12:08, 11 April 2010
- ==Search cases== ! align="center" style="background:#f0f0f0;" | Search Type24 KB (3,634 words) - 17:32, 24 November 2011
- ...sequential reads from a compacted or optimised index when finding a given search term. ...sult sets for particular terms must also be efficient: unlike conventional search solutions which may present pages of results and not attempt to provide a g6 KB (874 words) - 13:45, 14 July 2010
- ==Search cases== Search type: UniProt_Ac28 KB (4,119 words) - 14:30, 18 June 2010
- ==Search cases== Search type: UniProt_Ac28 KB (4,119 words) - 00:10, 19 June 2010
- ...archon=names&suite=all§ion=all Debian] and [http://packages.ubuntu.com/search?keywords=openjdk-6-jdk&searchon=names&suite=all§ion=all Ubuntu]. === Search for interactions involving “QCR2_HUMAN” ===31 KB (4,911 words) - 16:28, 6 July 2011
- * search function and evidence supporting interactions found,2 KB (293 words) - 13:47, 15 February 2011
- ...ed by the EntrezGene database). In those cases where no hit was found, the search was broadened to include synonyms and locus names for the gene name listed ...es, stand-alone digits and roman numerals are also removed. The resulting search strings are anchored at the beginning to select for partial title hits. Tw10 KB (1,459 words) - 11:55, 17 October 2011
