Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: test from netmaker #2993

Closed
1 task done
theguy951357 opened this issue Jun 26, 2024 · 0 comments
Closed
1 task done

[Bug]: test from netmaker #2993

theguy951357 opened this issue Jun 26, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@theguy951357
Copy link
Contributor

Contact Details

giggity@giggity.goo

What happened?

A bug happened! testing 1,2

Version

v0.24.2

What OS are you using?

No response

Relevant log output

Zobel's five points

* 		Abstract 
* 		An abstract is typically a single paragraph of about 50–200 words. The function of an abstract is
* 		to allow readers to judge whether or not the paper is of relevance to them. It should therefore be
* 		a concise summary of the paper’s aims, scope, and conclusions. There is no space for
* 		unnecessary text; an abstract should be kept to as few words as possible while remaining clear
* 		and informative. Irrelevancies, such as minor details or a description of the structure of the
* 		paper, are usually inappropriate, as are acronyms, mathematics, abbreviations, or citations. Only
* 		in rare circumstances should an abstract cite another paper (for example, when one paper
* 		consists entirely of analysis of results in another), in which case the reference should be given in
* 		full, not as a citation to the bibliography. Sentences such as “We review relevant literature” should
* 		be omitted. 
* 		Many abstracts follow a five-element organization:
* 		1. 
* 		A general statement introducing the broad research area of the particular topic being
* 		investigated. 
* 		2. 
* 		An explanation of the specific problem (difficulty, obstacle, challenge) to be solved. 
* 		3. 
* 		A review of existing or standard solutions to this problem and their limitations. 
* 		4. 
* 		An outline of the proposed new solution. 
* 		5. 
* 		A summary of how the solution was evaluated and what the outcomes of the evaluation were. 
* 		Thus a draft of an abstract can consist of five sentences, one for each of the points above.
* 		Introductions should be structured in much the same way, but with a paragraph or two, not a
* 		sentence, for each component. A valuable exercise is to read other papers, analyze their
* 		abstracts and introductions to see if they have this form, and then decide whether they are
* 		effective. 












* 		[
6:18 PM]



The more specific an abstract is, the more interesting it is likely to be. Instead of writing “space
* 		requirements can be significantly reduced”, for example, write “space requirements can be
* 		reduced by 60 %”. Instead of writing “we have a new inversion algorithm”, write “we have a new
* 		inversion algorithm, based on move-to-front lists”. 
* 		Many scientists browse research papers outside their area of expertise. You should notassume that all likely readers will be specialists in the topic of the paper—abstracts should be
* 		self-contained and written for as broad a readership as possible. 






Contributing guidelines

  • Yes, I did.
@theguy951357 theguy951357 added the bug Something isn't working label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants