You are here: wiki > Dynamics of a Surface Platform for Testing Hydrokinetic Turbines
Search Wiki
Find information by searching. The search will give suggestions as you type.

List by author

Parameters

Search options

 

 

General
You can search for any word(s) in articles and/or articles by a specific author

 

Boolean
WIKI supports Boolean search methodology. The boolean full-text search capability supports the following operators:

+
A leading plus sign indicates that this word must be present in each row that is returned.

-
A leading minus sign indicates that this word must not be present in any of the rows that are returned.

Note: The - operator acts only to exclude rows that are otherwise matched by other search terms. Thus, a boolean-mode search that contains only terms preceded by - returns an empty result. It does not return “all rows except those containing any of the excluded terms.”

(no operator)

By default (when neither + nor - is specified) the word is optional, but the rows that contain it are rated higher. This mimics the behavior of MATCH() ... AGAINST() without the IN BOOLEAN MODE modifier.


> <
These two operators are used to change a word's contribution to the relevance value that is assigned to a row. The > operator increases the contribution and the < operator decreases it. See the example following this list.


( )
Parentheses group words into subexpressions. Parenthesized groups can be nested.

 

~
A leading tilde acts as a negation operator, causing the word's contribution to the row's relevance to be negative. This is useful for marking “noise” words. A row containing such a word is rated lower than others, but is not excluded altogether, as it would be with the - operator.


*
The asterisk serves as the truncation (or wildcard) operator. Unlike the other operators, it should be appended to the word to be affected. Words match if they begin with the word preceding the * operator.

If a word is specified with the truncation operator, it is not stripped from a boolean query, even if it is too short (as determined from the ft_min_word_len setting) or a stopword. This occurs because the word is not seen as too short or a stopword, but as a prefix that must be present in the document in the form of a word that begins with the prefix. Suppose that ft_min_word_len=4. Then a search for '+word +the*' will likely return fewer rows than a search for '+word +the':

The former query remains as is and requires both word and the* (a word starting with the) to be present in the document.

The latter query is transformed to +word (requiring only word to be present). the is both too short and a stopword, and either condition is enough to cause it to be ignored.


"
A phrase that is enclosed within double quote (“"”) characters matches only rows that contain the phrase literally, as it was typed. The full-text engine splits the phrase into words and performs a search in the FULLTEXT index for the words. Nonword characters need not be matched exactly: Phrase searching requires only that matches contain exactly the same words as the phrase and in the same order. For example, "test phrase" matches "test, phrase".

If the phrase contains no words that are in the index, the result is empty. For example, if all words are either stopwords or shorter than the minimum length of indexed words, the result is empty.

 

EXAMPLES
The following examples demonstrate some search strings that use boolean full-text operators:

'apple banana'
Find rows that contain at least one of the two words.


'+apple +juice'
Find rows that contain both words.


'+apple macintosh'
Find rows that contain the word “apple”, but rank rows higher if they also contain “macintosh”.


'+apple -macintosh'
Find rows that contain the word “apple” but not “macintosh”.


'+apple ~macintosh'
Find rows that contain the word “apple”, but if the row also contains the word “macintosh”, rate it lower than if row does not. This is “softer” than a search for '+apple -macintosh', for which the presence of “macintosh” causes the row not to be returned at all.


'+apple +(>turnover Find rows that contain the words “apple” and “turnover”, or “apple” and “strudel” (in any order), but rank “apple turnover” higher than “apple strudel”.


'apple*'
Find rows that contain words such as “apple”, “apples”, “applesauce”, or “applet”.


'"some words"'
Find rows that contain the exact phrase “some words” (for example, rows that contain “some words of wisdom” but not “some noise words”). Note that the “"” characters that enclose the phrase are operator characters that delimit the phrase. They are not the quotation marks that enclose the search string itself. 


















Dynamics of a Surface Platform for Testing Hydrokinetic Turbines

2012-07-24 | From Toby Dewhurst

This scientific poster was presented at the First Annual INORE North American Symposium, June 17-21, 2012 at the Massachusetts Maritime Academy. 

Abstract:

The University of New Hampshire (UNH) Center for Ocean Renewable Energy (CORE), under funding from UMass Dartmouth, is investigating conceptual designs for a tidal hydrokinetic device test facility at Muskeget Channel, in coordination with the Edgartown Tidal Energy Project. The device development scale-up would progress from laboratory, to the UNH CORE site, then to Muskeget Channel for large systems. Three platform concepts are being investigated for testing hydrokinetic turbines of various sizes: A floating platform, a bottom-mounted gravity foundation, and a bottom-mounted pile foundation, which includes both a four-pile group and a two-pile surface-piercing structure that could raise and lower a device. A natural berth option is also being considered. Preliminary designs for each concept are being developed for structural soundness, vibration characteristics, scour, corrosion resistance, bio-fouling, connection to power take-off, monitoring considerations, ease of turbine installation and access, and cost. The designs are compared for the feasibility of their construction and the advantages they offer to turbine developers. 



Add your comment

You must be logged in to comment on content

bottom