1) The document provides instructions for preparing papers in single column format, including formatting guidelines for page layout, fonts, headings, paragraphs, tables, figures, and references.
2) Authors are requested to submit final papers electronically and to follow specific formatting guidelines for margins, fonts, headings, paragraphs, tables, figures, and references.
3) Key guidelines include using A4 page size with specified margins, Times New Roman font, numbered headings in bold and sections in sentence case, indented paragraphs, and providing figure and table captions.
With the Technological advancements, it is well understood that more and more objects are getting connected together. These objects are becoming more smarter to handle many operations through its inter connectivity. Rather than requiring devices to go through the network backbone infrastructure, fog computing permits devices to connect directly with their destination with ease and allows them to handle their connections and tasks. As a result, fog computing improves quality of service, reduces latency, and gives a more satisfactory user experience.
Fog computing or fog networking, also known as fogging, is an architecture that uses edge devices to carry out a substantial amount of computation, storage, and communication locally and routed over the internet backbone.
Presentation made at the Symposium on “Mainstreaming university-community research partnerships” at Indian Habitat Center on 9th April 2015, Organized by PRIA.
With the Technological advancements, it is well understood that more and more objects are getting connected together. These objects are becoming more smarter to handle many operations through its inter connectivity. Rather than requiring devices to go through the network backbone infrastructure, fog computing permits devices to connect directly with their destination with ease and allows them to handle their connections and tasks. As a result, fog computing improves quality of service, reduces latency, and gives a more satisfactory user experience.
Fog computing or fog networking, also known as fogging, is an architecture that uses edge devices to carry out a substantial amount of computation, storage, and communication locally and routed over the internet backbone.
Presentation made at the Symposium on “Mainstreaming university-community research partnerships” at Indian Habitat Center on 9th April 2015, Organized by PRIA.
http://www.HomePure.com
Mọi người đều biết nước là điều thiết yếu cho sự sống. Trái đất cần nước và chúng ta cũng vậy, nước ở xung quanh và bên trong cơ thể chúng ta, song vẫn có một số người chỉ dùng nước khi cần mà thôi. Khi nghiêm túc nói về chức năng sinh học mà nước đối với cơ thể con người thì tầm quan trọng của nước đóng vai trò then chốt.
New folderfac_lee023_HW06_WR5_FuncDecomp (3).pdfECE380 Pr.docxcurwenmichaela
New folder/fac_lee023_HW06_WR5_FuncDecomp (3).pdf
ECE380 Professional Seminar
Spring 2017
HW5 (WR5): Functional Decomposition
Date assigned: 3/13/17, Monday
Due date: Noon, 3/20/17, Monday
Max points: 20 pts.
Description:
Written Report 5 is on completing 3-level (i.e., Level 0, Level 1, and Level 2) functional
decomposition of your project. Each student shall individually submit one report that
shows complete functional decomposition of the project but also clearly identified
individual responsibilities for implementation. As such, all team members of a project
should first discuss and come up with a complete set of Level 1 subsystems that could be
implemented under balanced workloads among the team members. Then, each member
shall further elaborate his/her assigned Level 1 subsystems into Level 2.
This report should include block diagrams of all Level 0 ~ Level 2 subsystems and
corresponding tables of ALL subsystems with module name, inputs, outputs,
functionality (see pp. 93 ~ 98 of textbook by Ford and Coulston), AND responsible team
member.
Submission instructions:
Report length: No limit
How to submit: Upload onto EvalTools by the deadline shown above.
Grading:
Overall functional decomposition – team performance
Subsystems – individual performance
New folder/fac_lee023_HW11_WR6_FinalReport (1) (1).pdf
ECE380 Professional Seminar
Spring 2017
HW11: Final Report
Date assigned: 4/10/16, Monday
Due date: Noon, Monday, 4/24/17
Max points: 100 pts.
Description:
Each team’s final report must contain properly revised details of all project aspects covered
in this course, i.e., marketing and engineering requirements, proper description of the
project, 3-level functional decomposition, and project management including a well-
planned project plan presented in a Gantt chart.
To give incentive to a proper revision of functional decomposition, the final report will
carry 100 points of which 40 points will be allocated to the revised functional
decomposition (presented within the final report). Gantt chart (presented within the final
report) will have 10 points among the total of 100 points for the final report. The rest 50
points will go to the overall quality of the report as described in the review criteria.
Submission instructions:
Final Reports are team submissions so each document shall have all team member names
and only one person in the team shall upload the report to the designated submission link.
New folder/fac_lee023_HW11_WR6_FinalRpt_Guideline (1) (1).docxFinal Project Report Title ECE 380 Professional Seminar
by
Author(s) Name(s)
Author Affiliation(s)
E-mail
Date
Department of Electrical and Computer Engineering
Gannon University, Erie, PA
Acknowledgement
If you have any positive remarks this is the place to show your gratitude.
Abstract
The abstract is to be in fully-justified italicized text, as it is here, ...
Sample IEEE Paper for A4 Page Size First Author#1, Sec.docxrtodd599
Sample IEEE Paper for A4 Page Size
First Author
#1
, Second Author
*2
, Third Author
#3
#
First-Third Department, First-Third University
Address Including Country Name
1
[email protected]
3
[email protected]
*
Second Company
Address Including Country Name
2
[email protected]
Abstract— This document gives formatting instructions for
authors preparing papers for publication in the Proceedings of
an IEEE conference. The authors must follow the instructions
given in the document for the papers to be published. You can
use this document as both an instruction set and as a template
into which you can type your own text.
Keywords— Put your keywords here, keywords are separated by
comma.
I. INTRODUCTION
This document is a template. An electronic copy can be
downloaded from the conference website. For questions on
paper guidelines, please contact the conference publications
committee as indicated on the conference website.
Information about final paper submission is available from the
conference website.
II. PAGE LAYOUT
An easy way to comply with the conference paper
formatting requirements is to use this document as a template
and simply type your text into it.
A. Page Layout
Your paper must use a page size corresponding to A4
which is 210mm (8.27") wide and 297mm (11.69") long. The
margins must be set as follows:
• Top = 19mm (0.75")
• Bottom = 43mm (1.69")
• Left = Right = 14.32mm (0.56")
Your paper must be in two column format with a space of
4.22mm (0.17") between columns.
III. PAGE STYLE
All paragraphs must be indented. All paragraphs must be
justified, i.e. both left-justified and right-justified.
A. Text Font of Entire Document
The entire document should be in Times New Roman or
Times font. Type 3 fonts must not be used. Other font types
may be used if needed for special purposes.
Recommended font sizes are shown in Table 1.
B. Title and Author Details
Title must be in 24 pt Regular font. Author name must be
in 11 pt Regular font. Author affiliation must be in 10 pt Italic.
Email address must be in 9 pt Courier Regular font.
TABLE I
FONT SIZES FOR PAPERS
Appearance (in Time New Roman or Times) Font
Size Regular Bold Italic
8 table caption (in
Small Caps),
figure caption,
reference item
reference item
(partial)
9 author email address
(in Courier),
cell in a table
abstract
body
abstract heading
(also in Bold)
10 level-1 heading (in
Small Caps),
paragraph
level-2 heading,
level-3 heading,
author affiliation
11 author name
24 title
All title and author details must be in single-column format
and must be centered.
Every word in a title must be capitalized except for short
minor words such as “a”, “an”, “and”, “as”, “at”, “by”, “for”,
“from”, “if”, “in”, “into”, “on”, “or”, “of”, “the”, “to”, “with”.
Author details must not show any professional title (e.g.
Managing Direct.
Sample IEEE Paper for A4 Page Size First Author#1, Sec.docxjeffsrosalyn
Sample IEEE Paper for A4 Page Size
First Author
#1
, Second Author
*2
, Third Author
#3
#
First-Third Department, First-Third University
Address Including Country Name
1
[email protected]
3
[email protected]
*
Second Company
Address Including Country Name
2
[email protected]
Abstract— This document gives formatting instructions for
authors preparing papers for publication in the Proceedings of
an IEEE conference. The authors must follow the instructions
given in the document for the papers to be published. You can
use this document as both an instruction set and as a template
into which you can type your own text.
Keywords— Put your keywords here, keywords are separated by
comma.
I. INTRODUCTION
This document is a template. An electronic copy can be
downloaded from the conference website. For questions on
paper guidelines, please contact the conference publications
committee as indicated on the conference website.
Information about final paper submission is available from the
conference website.
II. PAGE LAYOUT
An easy way to comply with the conference paper
formatting requirements is to use this document as a template
and simply type your text into it.
A. Page Layout
Your paper must use a page size corresponding to A4
which is 210mm (8.27") wide and 297mm (11.69") long. The
margins must be set as follows:
• Top = 19mm (0.75")
• Bottom = 43mm (1.69")
• Left = Right = 14.32mm (0.56")
Your paper must be in two column format with a space of
4.22mm (0.17") between columns.
III. PAGE STYLE
All paragraphs must be indented. All paragraphs must be
justified, i.e. both left-justified and right-justified.
A. Text Font of Entire Document
The entire document should be in Times New Roman or
Times font. Type 3 fonts must not be used. Other font types
may be used if needed for special purposes.
Recommended font sizes are shown in Table 1.
B. Title and Author Details
Title must be in 24 pt Regular font. Author name must be
in 11 pt Regular font. Author affiliation must be in 10 pt Italic.
Email address must be in 9 pt Courier Regular font.
TABLE I
FONT SIZES FOR PAPERS
Appearance (in Time New Roman or Times) Font
Size Regular Bold Italic
8 table caption (in
Small Caps),
figure caption,
reference item
reference item
(partial)
9 author email address
(in Courier),
cell in a table
abstract
body
abstract heading
(also in Bold)
10 level-1 heading (in
Small Caps),
paragraph
level-2 heading,
level-3 heading,
author affiliation
11 author name
24 title
All title and author details must be in single-column format
and must be centered.
Every word in a title must be capitalized except for short
minor words such as “a”, “an”, “and”, “as”, “at”, “by”, “for”,
“from”, “if”, “in”, “into”, “on”, “or”, “of”, “the”, “to”, “with”.
Author details must not show any professional title (e.g.
Managing Direct.
Paper Title (use style paper title)Note Sub-titles are not.docxaman341480
Paper Title* (use style: paper title)
*Note: Sub-titles are not captured in Xplore and should not be used
line 1: 1st Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 4th Given Name Surname
line 2: dept. name of organization(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 2nd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 5th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 3rd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 6th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
Abstract—This electronic document is a “live” template and already defines the components of your paper [title, text, heads, etc.] in its style sheet. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes, or Math in Paper Title or Abstract. (Abstract)
Keywords—component, formatting, style, styling, insert (key words)
I. Introduction (Heading 1)
This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow.
II. Ease of Use
A. Selecting a Template (Heading 2)
First, confirm that you have the correct template for your paper size. This template has been tailored for output on the A4 paper size. If you are using US letter-sized paper, please close this file and download the Microsoft Word, Letter file.
B. Maintaining the Integrity of the Specifications
The template is used to format your paper and style the text. All margins, column widths, line spaces, and text fonts are prescribed; please do n.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Designing Great Products: The Power of Design and Leadership by Chief Designe...
Rtetmsd format1
1. Preparation of papers in single column format
A B Author1
, C D Author2
and E F Author3
1
Department, University,
Street, Town, City, COUNTRY
2,3
Department, Company,
Street, Town, City, COUNTRY
1
ab@etc,
2
cd@etc,
3
ef@etc
1
www.website.1.etc,
2
www. website.2.etc,
3
www. website.3.etc
ABSTRACT
This electronic document is a “live” template. The various components of your paper [title, text, heads, etc.] are already defined on
the style sheet, as illustrated by the portions given in this document. DO NOT USE SPECIAL CHARACTERS, SYMBOLS, OR
MATH IN YOUR TITLE OR ABSTRACT. (Abstract)
Keywords-component; formatting; style; styling; insert (key words)
1. INTRODUCTION
Authors are requested to submit the final formatted paper electronically. The paper is to be formatted for PC, with either a
Rich Text Format or Word for Windows PC (preferably Word97 or higher). Please do not send password protected files.
Authors are fully responsible for the quality of their article and are kindly requested to observe the following instructions
for the preparation of their manuscripts.
2. FORMATS FOR PAPERS
2.1 Full-size Electronic & Camera Ready Copy (CRC) Manuscripts
If you use Word, prepare your paper in full-size format using A4 setting (210mm 297mm) and check the different even
and odd pages. Do not use local paper sizes. In formatting the page, set the margins to those shown in Table 1. Do not use
any headers or footers, or change those present in this template. Avoid using footnotes. Wear sunscreen (a joke to alleviate
the tedium of these instructions). Other word processing should follow as close as possible the format given and saved as
Rich Text Format (RTF).
Table 1. The caption comes before the table, italicised and centred on the page.
left margin: 2.5 cm top margin: 2.0 cm
right margin: 2.5 cm bottom margin: 3.0 cm
header: 1.0 cm gutter: 0.5 cm
footer: 1.5 cm gutter position: left
2.2 Electronic Submission of Papers
Authors are asked to submit the final versions of papers electronically to the Organizing Secretary at
conference.mvn@gmail.com. Use international fonts and avoid the use of local fonts. Submit in Word or RTF form only.
2. 3. UNITS
The standard units of the conference follow IEEE guidelines. Please use SI units as primary units. Please avoid using any
other units unless they are used as identifiers in trade.
4. HEADINGS, PARAGRAPHS AND TYPE FONTS
The easiest way to format the paper is to use this document as a template for your paper – see attached. Please do not
alter the footer information.
The main heading of the paper should be in sentence case and centred. Avoid starting the title by using indefinite
articles (a, an, to, the, etc). Do not use abbreviations or acronyms in the title. This heading should be in bold using 14 point
type size. The title should be preceded by a 24 point spacing (usage of Format Paragraph is encouraged).
Section heading should also be bold and centred, but capitalised, in 12 point type size. The spacing preceding the
section headings is 16 point. All sections (except the Abstract and Acknowledgements, if any) should be consecutively
numbered, including Conclusions and References.
4.1 Subheadings and Initial Letters
Subheadings should be 10 point, italicised, typed flush to left side, and in lower case with initial capitals for all
main words. Number each subheading as shown using the section number and subheading number.
Subheadings and sub-subheadings here are preceded by a single line space (10 point).
4.1.1 Sub-subheadings. Sub-subheadings should be typed as for subheadings. The following text should run on after the full
stop. There should not be any further layers.
4.2 Paragraphs
Any paragraph starting after a heading, subheading, table, figure or equation, should begin flush with the left column.
Subsequent columns should be indented by 5mm, as follows:
Type size for standard text (and all subheadings) should be 10 point, the line spacing should be set at ‘at least 10 point’.
There should be a 6 point spacing between paragraphs.
4.3 Fonts
The default font for the Proceedings should be in Times New Roman. Other fonts are acceptable for use in diagrams or
tables. However, do not use any fonts that are region specific. If in doubt please email the Organizing Secretary to ensure
compatibility of the font you wish to use.
5.STYLE HINTS
5.1 First Page
Space between the Title and Abstract is reserved for the name(s) of author(s), affiliation(s), corresponding address(es),
email address(es) and, if appropriate, web site. Abstract, keywords and main body of the paper follow as suggested by this
manuscript. The abstract should be not more than 300 words; three to seven keywords should be provided, indicating the
main topics discussed within the paper. These will be used to provide basic terms for indexing. As with the title, please
avoid abbreviations and acronyms. Also try not to give too general keywords (for example Virtual Reality).
5.2 Do Not Start a Section of Subheading at the end of a page.
3. 5.3 Drawings and Illustrations
Where possible use computer generated figures and images that can be incorporated directly into the soft copy versions of
the paper. Please note that coloured lines and photographs may not reproduce well in the final printed form as the
proceedings will be printed in black and white. Illustrations and photographs should be positioned at or near the top of a
page and as close as possible to the first reference to them. Please note, if you must submit a Camera Ready Copy version,
that B&W photographs will look considerable better if they are first transferred to bromide prints. The following points
should be carefully noted:
Microsoft Object Editing. It cannot be emphasised enough that the use of frames to position images, tables or
drawings should be avoided if at all possible, as should the generation of diagrams and tables using Microsoft
Picture Editing tools.
If possible please generate tables using the Table tool and generate any other diagrams using separate software,
saving diagrams as images (JPEG, GIF, TIFF, etc).
Captions for tables should appear before the table, see Table 1, while captions for figures and photographs should
appear after the figure, see Fig. 1, for example. Both should be centred and italicised. Long captions should be justified with
1cm right and left margins.
Figure 1. The caption comes after the illustration or photograph and is centred. Any diagram or figure that has
been previously published should be referenced. This photograph appears courtesy of [Sharkey, 1996].
5.3 Equations
Equations should be typed within the text and numbered consecutively throughout the manuscript. The equation number
should be typed in parenthesis, flush with the right hand margin. Equations may be centred with each other, see Eqs (12)
or on the page, see Eq. (3). Note that equations need not be numbered.
Theorem 1. The dynamic system given by
x A x A z
z A x A z B u
11 12
21 22 2
(1)
(2)
may be represented by the reduced order representation, for time t > t
*
> to,
x A A A A x
s s
11 12 22
1
21
iff the matrix A22 has negative eigenvalues and the small parameter, > 0, is less than
*
<< 1.
Proof: The proof is not trivial, but might be presented in about 2 pages.
5.4 Referencing Other Work
4. When referring to previous work, the surname of the first author and the year of publication of the reference should be
given. Two or more references by the same author in the same year should be differentiated by letters a, b, c, etc. For
references of more than two authors, text citations should be shortened to the first name followed by the term et al.
Examples: Smith (1959, 1961a,b, 1962a) describes a method for ... New theorems (Smith and Jones, 1963; Smith et al, 1964)
in this field were ...
Only essential references which are directly referred to in the text should be included in the reference list. The
references should be listed in alphabetical order in the list at the end of the paper. References by the same author(s) should
be listed in chronological order.
References should include: author’s initials and surname, initials and surnames of remaining authors, year of publication
in parenthesis, article title, abbreviated journal title in italics, volume number in bold, issue number in italics, and page
numbers. For conference articles name the city in which the conference was held. Include the country if the city is not well
known. In case of reference to a book, the book title should be italicised, and the publisher and place of publication should
be included.
See example Reference section below.
6.CONCLUSIONS
Once your manuscript has been submitted, it will be impossible to make any corrections or alterations to it. Therefore,
please ensure that your paper is sent to the Organizing Secretary at conference.mvn@gmail.com only after you have
thoroughly checked and approved it.
Finally please observe the following instructions:
1. Ensure that your paper is in the correct format, and is maximum of 4 pages, inclusive of illustrations.
2. Keep a copy of your manuscript.
Acknowledgements: If any acknowledgements are required please insert after the conclusions to the paper using this
format.
7.REFERENCES
A N Author, B O Author and C I Author (1990), Article in a regular journal, Intl. J. Autom. Control, 4, 11, pp. 231245.
A N Author, B O Author and C I Author (1990), Article in conference, Proc. IEEE Intl. Conf. Autom. Control, Atlanta, pp.
231245.
B Scribe and C Author (1987), Article in an edited book, In Book Title (B Brown & G Green, Eds), Ironing Press, London, pp.
231245.
A Writer (1993), Book Title, Ironing Press, London.
P M Sharkey (1996), Yorick 85CR (my robot head), University of Reading, UK.
5. Title
A B Author1
, C D Author2
and E F Author3
1
Department, University,
Street, Town, City, COUNTRY
2,3
Department, Company,
Street, Town, City, COUNTRY
1
ab@etc,
2
cd@etc,
3
ef@etc
1
www.institute1.country,
1
www.institute1.country,
1
www.institute1.country
ABSTRACT
Text
1. INTRODUCTION
First paragraph text.
Subsequent paragraph text.
2. SECTIONS
2.1 Subheading
First paragraph text.
Subsequent paragraph text.
Table 1. Table Caption.
TABLE here
4.1.1 Sub-subheadings. Text.
Itemised lists:
Item title. Text
IMAGE or DIAGRAM here.
Figure 1. Long caption format.
Figure 1. Short caption format.
Equation box
Equation (number)
6. 3.CONCLUSIONS
First paragraph text.
Subsequent paragraph text.
Acknowledgements: Text.
4.REFERENCES
A N Author, B O Author and C I Author (1990), Article in a regular journal, Intl. J. Autom. Control, 4, 11, pp. 231245.
A N Author, B O Author and C I Author (1990), Article in conference, Proc. IEEE Intl. Conf. Autom. Control, Atlanta, pp.
231245.
B Scribe and C Author (1987), Article in an edited book, In Book Title (B Brown & G Green, Eds), Ironing Press, London, pp.
231245.
A Writer (1993), Book Title, Ironing Press, London.