Matlab

Be sure that the symbols in your equation have been defined before the equation appears or immediately following. Italicize symbols (T might refer to temperature, but T is the unit tesla). Refer to “(1),” not “Eq. (1)” or “equation (1),” except at the beginning of a sentence: “Equation (1) is ... .”

References

References are listed in the order they appear, not in alphabetical order. Number citations consecutively in square brackets [1]. The sentence punctuation follows the brackets [2]. Multiple references [2], [3] are each numbered with separate brackets [1]–[3]. When citing a section in a book, please give the relevant page numbers [2]. In sentences, refer simply to the reference number, as in [3]. Do not use “Ref. [3]” or “reference [3]” except at the beginning of a sentence: “Reference [3] shows ... .” Please do not use automatic endnotes in Word, rather, type the reference list at the end of the paper using the “References” style.

Number footnotes separately in superscripts (Insert | Footnote).[footnoteRef:3] Place the actual footnote at the bottom of the column in which it is cited; do not put footnotes in the reference list (endnotes). Use letters for table footnotes (see Table I). [3: It is recommended that footnotes be avoided (except for the unnumbered footnote with the receipt date on the first page). Instead, try to integrate the footnote information into the text.]

Please note that the references at the end of this document are in the preferred referencing style. Give all authors’ names; do not use “et al.” unless there are six authors or more. Use a space after authors’ initials. Papers that have not been published should be cited as “unpublished” [4]. Papers that have been accepted for publication, but not yet specified for an issue should be cited as “to be published” [5]. Papers that have been submitted for publication should be cited as “submitted for publication” [6]. Please give affiliations and addresses for private communications [7].

Capitalize only the first word in a paper title, except for proper nouns and element symbols. For papers published in translation journals, please give the English citation first, followed by the original foreign-language citation [8].

Sections

Your introduction will need to introduce the contents of the paper, it will also briefly describe all the following sections with a sentence or two about each section.

Program operation and game simulation

Put an introduction paragraph here so that you can link the two following concepts (a) operation of the program and (b) how it simulates the game.

Program Operation

Describe your program and make use of the flowchart and structure chart you have included. Crasimperdiet, nequeaaccumsanelementum, tellus dui sagittiselit, sit ameteleifend dui mi et risus. In vitae diampellentesque, blanditnullanon, portanunc. Praesentvulputate, nisletultricesullamcorper, nisi est semper mauris, at facilisissemipsum in lectus. Maecenas nuncfelis, ultricies sit ameteuismodluctus, laciniaposuere ligula. Aenean vitae metustortor. Donecsuscipitdiamquisjustopharetra, in pharetraurnafermentum. Curabiturbibendummollisultricies. Vivamus non massaegeturnafeugiatsuscipit. Etiamquisscelerisquerisus.

Quisquedignissim, tortoradipiscinginterdum tempus, nuncvelitcondimentumjusto, non volutpatorcifelis id sem. Donectortormassa, cursuseujusto id, vulputateporttitormassa. Sedscelerisque lacus eget dui rutrum, velporttitorloremtincidunt. Cras sit ametimperdieteros. Donecportaipsumvelenimconvallis, egetfacilisisnequescelerisque. Nuncplaceratsodaleselit in tincidunt. Nunc ac justoturpis. Aenean a esterat. Duisvolutpatconsecteturnisl id hendrerit. Aeneanvelfelisodio. Sedvolutpaterat lacus.

Fig. 1. Structure chart from data processing program. The main programcalls function blah() to perform the blahing of the data while there yada-ingusing function yada(). Stuff is performed through the use of abc() with deffingperformed by def().

Pellentesquesedportanibh. Sedsodalesnuncsedaliquaminterdum. Doneceuluctusrisus, eupharetrasapien. Duisturpislibero, molestieetorcivel, tempus rhoncusarcu. Etiamscelerisque dolor id rhoncuspharetra. Donec vitae ullamcorpernisl. Utetaccumsan quam. Suspendissecongueelitultriceslectusporta, euvestibulumfelisdapibus. Morbi id tortorconsectetur, accumsanest a, hendreritneque. Suspendisseconsequatornarejusto, sit ametadipiscingnislullamcorperquis. Uteufelisvehicula, temporfelis a, temporenim. Proin sit amet quam gravida, egestassapien in, fermentumrisus.

Game Simulation

Explain the key aspects of the game and how your program implements each section. Having described the program in the previous section this section should be able to refer back to the descriptions above.

Fig. 2. Badly Drawn Flow Chart of the data processing of the sensor data toproduce the plots of yadayada and blahblah using the ipsofactor of the case ofthe musical cow.

Suspendisselobortis, dolor laoreetaccumsanfringilla, augue quam cursusleo, egetelementumnibhlibero in enim. Phasellusluctusenim at tempus commodo. Aeneanquislaciniasapien. Nam imperdietodioeumassamattis, a ultriciesnuncfacilisis. Pellentesque a faucibus nisi, egetmolestiepurus. Praesentvolutpatmollisvelit, in ornareliberoblanditeu. Morbifacilisisvestibulumscelerisque.

Ut at augueturpis. Vestibulum a tortor vitae mi tinciduntaccumsan. Utsodalesvelit a luctusfermentum. Vivamus ligula odio, suscipitetfermentumeget, dignissim id arcu. Doneceuvolutpatmassa. Nullam vitae nislelit. Nam sit ameteleifenderos. Nuncvariusdapibusfelis id cursus. Integer velnulla id mi fringillaporta. Maecenas iaculisvehicula lacus, vitae rhoncusestvolutpatut. Cum sociisnatoquepenatibusetmagnis dis parturient montes, nasceturridiculus mus. Morbimattismolestieaugue, aliquetegestasipsumconguenec. Sediaculis, lectusvelvehiculavenenatis, lorem nisi accumsanturpis, id varius quam libero vitae tortor. Quisque a variusurna.

Testing

The section on testing should describe (a) what you tested and (b) how you tested it. For example if testing a game simulation you might want to test the simplicity of operation with user feedback. You could do this by getting a number of people to test it and record their responses. You will need to test the correct operation of the game, there may even be laws it has to comply with. You need to identify the requirements and how you designed the test to ensure it was correctly testing the requirements. You may want to include a table of the different tests being performed. Each item in the list of tests should have a matching item in the results section.

( Fig. 3 . Magnetization as a function of applied field. Note that “Fig.” is abbreviated. There is a period after the figure number, followed by two spaces. It is good practice to explain the significance of the figure in the caption. ) ( TABLE I Units for Magnetic Properties Symbol Quantity Conversion from Gaussian and CGS EMU to SI a magnetic flux 1 Mx 10 8 Wb = 10 8 V·s B magnetic flux density, magnetic induction 1 G 10 4 T = 10 4 Wb/m 2 H magnetic field strength 1 Oe 10 3 /(4 ) A/m m magnetic moment 1 erg/G = 1 emu 10 3 A·m 2 = 10 3 J/T M magnetization 1 erg/(G·cm 3 ) = 1 emu/cm 3 10 3 A/m 4 M magnetization 1 G 10 3 /(4 ) A/m specific magnetization 1 erg/(G·g) = 1 emu/g 1 A·m 2 /kg j magnetic dipole moment 1 erg/G = 1 emu 4 10 10 Wb·m J magnetic polarization 1 erg/(G·cm 3 ) = 1 emu/cm 3 4 10 4 T , susceptibility 1 4 mass susceptibility 1 cm 3 /g 4 10 3 m 3 /kg permeability 1 4 10 7 H/m = 4 10 7 Wb/(A·m) r relative permeability r w, W energy density 1 erg/cm 3 10 1 J/m 3 N, D demagnetizing factor 1 1/(4 ) Vertical lines are optional in tables. Statements that serve as captions for the entire table do not need footnote letters. a Gaussian units are the same as cgs emu for magnetostatics; Mx = maxwell, G = gauss, Oe = oersted; Wb = weber, V = volt, s = second, T = tesla, m = meter, A = ampere, J = joule, kg = kilogram, H = henry. )

Results

For every test described in testing there should be a matching set of results. Results can be a mix of words and tables and even images. For example if a game simulation requires a range of outcomes each with a particular probability, the calculated probability could be listed along with the tested result. The testing may just include an item describing that it is testing the correct probabilities and how it is testing the probabilities. In the results they may be a table with a list of outcomes and their probability and the test results. Results for a user feedback test may include an image of which aspect a user found difficult and how this was improved to get better feedback results.

The results are not discussed here, just presented along with any useful additional information.

Discussion

This is where results are discussed. Positive and negative results are discussed and the issues causing negative results are examined. The discussion should also examine how the requirements or needs identified in the introduction were achieved (or not achieved)

Any identified issues and shortcomings should be listed along with the cause. These could then be discussed in further detail in a dedicated subsection (using a Heading 2 style). Where discussing failures and partially functioning solutions, identify the cause and the work necessary to rectify the problem. This can be reasonably detailed.

Future Work

If additional work is required to resolve major issues or a list of minor issues, briefly describe the process and expectation for success.

Conclusion

Summarize the situation. A certain proposal was made, a solution was hypothesized. This solution was successful, partially successful, a failure. These lessons were learnt.

Appendix

If various items are added as an appendix, identify them here. They should not be inserted here unless it is a short reference table or text list of items. Large items such as code printouts and screen images should be identified here and attached as separate documents. It is too difficult to add those items and format them.

Acknowledgment

Don't include this section unless you have a specific acknowledgement. If you discussed this project with someone and they significantly aided your understanding or suggested a specific method of solving your problem, acknowledge them and their assistance.

Other Recommendations& common mistakes

Use one space after periods and colons. Hyphenate complex modifiers: “zero-field-cooled magnetization.” Avoid dangling participles, such as, “Using (1), the potential was calculated.” [It is not clear who or what used (1).] Write instead, “The potential was calculated by using (1),” or “Using (1), we calculated the potential.”

Use a zero before decimal points: “0.25,” not “.25.” Use “cm3,” not “cc.” Indicate sample dimensions as “0.1 cm 0.2 cm,” not “0.1 0.2 cm2.” The abbreviation for “seconds” is “s,” not “sec.” Do not mix complete spellings and abbreviations of units: use “Wb/m2” or “webers per square meter,” not “webers/m2.” When expressing a range of values, write “7 to 9” or “7-9,” not “7~9.”

A parenthetical statement at the end of a sentence is punctuated outside of the closing parenthesis (like this). (A parenthetical sentence is punctuated within the parentheses.) In American English, periods and commas are within quotation marks, like “this period.” Other punctuation is “outside”! Avoid contractions; for example, write “do not” instead of “don’t.” The serial comma is preferred: “A, B, and C” instead of “A, B and C.”

Write in the past tense using the third person, for example don't write (“I observed that ...” or “We observed that ...” instead write“It was observed that ...”). Remember to check spelling. If your native language is not English, please get a native English-speaking colleague to carefully proofread your paper.

Some Common Mistakes

The word “data” is plural, not singular. The subscript for the permeability of vacuum µ0 is zero, not a lowercase letter “o.” The term for residual magnetization is “remanence”; the adjective is “remanent”; do not write “remnance” or “remnant.” Use the word “micrometer” instead of “micron.” A graph within a graph is an “inset,” not an “insert.” The word “alternatively” is preferred to the word “alternately” (unless you really mean something that alternates). Use the word “whereas” instead of “while” (unless you are referring to simultaneous events). Do not use the word “essentially” to mean “approximately” or “effectively.” Do not use the word “issue” as a euphemism for “problem.” When compositions are not specified, separate chemical symbols by en-dashes; for example, “NiMn” indicates the intermetallic compound Ni0.5Mn0.5 whereas “Ni–Mn” indicates an alloy of some composition NixMn1-x.

Be aware of the different meanings of the homophones “affect” (usually a verb) and “effect” (usually a noun), “complement” and “compliment,” “discreet” and “discrete,” “principal” (e.g., “principal investigator”) and “principle” (e.g., “principle of measurement”). Do not confuse “imply” and “infer.”

Prefixes such as “non,” “sub,” “micro,” “multi,” and “ultra” are not independent words; they should be joined to the words they modify, usually without a hyphen. There is no period after the “et” in the Latin abbreviation “et al.” (it is also italicized). The abbreviation “i.e.,” means “that is,” and the abbreviation “e.g.,” means “for example” (these abbreviations are not italicized).

References

[1] G. O. Young, “Synthetic structure of industrial plastics (Book style with paper title and editor),” in Plastics, 2nd ed. vol. 3, J. Peters, Ed. New York: McGraw-Hill, 1964, pp. 15–64.

[2] W.-K. Chen, Linear Networks and Systems (Book style). Belmont, CA: Wadsworth, 1993, pp. 123–135.

[3] H. Poor, An Introduction to Signal Detection and Estimation. New York: Springer-Verlag, 1985, ch. 4.

[4] B. Smith, “An approach to graphs of linear forms (Unpublished work style),” unpublished.

[5] E. H. Miller, “A note on reflector arrays (Periodical style—Accepted for publication),” IEEE Trans. Antennas Propagat., to be published.

[6] J. Wang, “Fundamentals of erbium-doped fiber amplifiers arrays (Periodical style—Submitted for publication),” IEEE J. Quantum Electron., submitted for publication.

First A. Author (M’76–SM’81–F’87) and the other authors may include biographies at the end of regular papers. Biographies are often not included in conference-related papers. This author became a Member (M) of IEEE in 1976, a Senior Member (SM) in 1981, and a Fellow (F) in 1987. The first paragraph may contain a place and/or date of birth (list place, then date). Next, the author’s educational background is listed. The degrees should be listed with type of degree in what field, which institution, city, state, and country, and year degree was earned. The author’s major field of study should be lower-cased.

The second paragraph uses the pronoun of the person (he or she) and not the author’s last name. It lists military and work experience, including summer and fellowship jobs. Job titles are capitalized. The current job must have a location; previous positions may be listed without one. Information concerning previous publications may be included.

.

)

(

)

(

)

|

|

(

exp

)]

2

(

/

[

)

,

(

0

2

1

1

0

0

2

0

2

l

l

l

l

l

m

s

j

j

d

r

J

r

J

z

z

r

d

dr

r

F

i

i

j

r

-

¥

-

-

×

=

ò

ò