Manual: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
= FLOODS/FLOOPS Introduction = | = FLOODS/FLOOPS Introduction = | ||
This manual is broken into several sections describing the commands that make up the '''FL'''orida '''O'''bject '''O'''riented '''D'''evice and '''P'''rocess '''S'''imulator. ... | This manual is broken into several sections describing the commands that make up the '''FL'''orida '''O'''bject '''O'''riented '''D'''evice and '''P'''rocess '''S'''imulator. FLOOXS uses the old unix wild card convention of x taking the place of either "P" or "D". The codes are built as a single executable and are configured with different sets of default variables for each purpose. New work in the [http://www.reliability.ece.ufl.edu Reliability MURI] is aimed at combining the codes to understand device operation driven failure modes. | ||
Commands in the manual are documented individually. It is best to start with examples that are similar to what you wish to do. These are linked to individual command descriptions for more detailed followup. The command list is also provided as a reference directly, if you are interested in more detail on the commands. | |||
All of FLOODS/FLOOPS is built using tcl. A familiarity with tcl commands is essential for understanding how to do anything complex in FLOOPS and FLOODS. You can find many great tcl reference books and [http://www.tcl.tk/man/tcl8.5/TclCmd/contents.htm tcl command documentation] is also available. | |||
= Examples = | |||
These are examples and working through them is the best way to learn. I usually use the homework problems to help students to start (answers are not provided!). Mastery of these exposes users to basic concepts. Beyond these are examples of increasing complexity. Each subsequent section makes use of concepts from prior examples. | |||
== [[Homework Problems]]== | |||
These are good introductory problems for beginners. Being able to work through these will introduce most simple concepts to users. | |||
== [[Grid Generation]]== | |||
These are worked examples of grid generation concepts. Build 1D, 2D, and 3D structures for simulation. | |||
== [[Post Processing]]== | |||
Although not as fancy as commercial tools, there are a wide range of ways to examine output results. Examples of analysis can be found in this section. | |||
== [[Alagator Examples]]== | |||
Alagator is the scripting language that controls the physics of the simulation. This is where the real power of floops and floods lies. | |||
== [[Device Examples]]== | |||
Examples that use alagator to investigate device performance. | |||
== [[Process Examples]]== | |||
Examples that use alagator and default scripts to simulate IC processing. | |||
= Command Reference = | |||
This contains a command reference, in Unix man page style for each command in the program. | |||
==[[Command Conventions]]== | |||
Some basic ideas on how commands work and are used. | |||
==[[Grid Commands]]== | |||
Commands to control grid generation and refinement. | |||
==[[Post Processing Commands]]== | |||
Commands to analyze data. | |||
==[[Application Specific Commands]]== | |||
Commands to solve systems of equations, deposit materials, and more! | |||
==[[Other Commands]]== | |||
Miscellaneous commands that aren't really categorizable. There are many useful commands here! | |||
| Line 18: | Line 42: | ||
* [[New Developments]] - A brief list of the new enhancements since the last release. | * [[New Developments]] - A brief list of the new enhancements since the last release. | ||
* [[Bugs]] - A list of current FLOOXS | * [[Bugs]] - A list of current FLOOXS Bugs that need action | ||
* [["To Do" List]] - Needed code enhancements | * [[ToDo|"To Do" List]] - Needed code enhancements for specific actions | ||
| Line 34: | Line 58: | ||
The tcl/tk package is in the public domain, and was developed by John Ousterhout at the University of California Berkeley. | The tcl/tk package is in the public domain, and was developed by John Ousterhout at the University of California Berkeley. | ||
Various included linear algebra packages are also public domain. | |||
== Getting started with Wiki == | == Getting started with Wiki == | ||
Revision as of 12:55, 11 September 2008
FLOOXS Main Page
FLOODS/FLOOPS Introduction
This manual is broken into several sections describing the commands that make up the FLorida Object Oriented Device and Process Simulator. FLOOXS uses the old unix wild card convention of x taking the place of either "P" or "D". The codes are built as a single executable and are configured with different sets of default variables for each purpose. New work in the Reliability MURI is aimed at combining the codes to understand device operation driven failure modes.
Commands in the manual are documented individually. It is best to start with examples that are similar to what you wish to do. These are linked to individual command descriptions for more detailed followup. The command list is also provided as a reference directly, if you are interested in more detail on the commands.
All of FLOODS/FLOOPS is built using tcl. A familiarity with tcl commands is essential for understanding how to do anything complex in FLOOPS and FLOODS. You can find many great tcl reference books and tcl command documentation is also available.
Examples
These are examples and working through them is the best way to learn. I usually use the homework problems to help students to start (answers are not provided!). Mastery of these exposes users to basic concepts. Beyond these are examples of increasing complexity. Each subsequent section makes use of concepts from prior examples.
Homework Problems
These are good introductory problems for beginners. Being able to work through these will introduce most simple concepts to users.
Grid Generation
These are worked examples of grid generation concepts. Build 1D, 2D, and 3D structures for simulation.
Post Processing
Although not as fancy as commercial tools, there are a wide range of ways to examine output results. Examples of analysis can be found in this section.
Alagator Examples
Alagator is the scripting language that controls the physics of the simulation. This is where the real power of floops and floods lies.
Device Examples
Examples that use alagator to investigate device performance.
Process Examples
Examples that use alagator and default scripts to simulate IC processing.
Command Reference
This contains a command reference, in Unix man page style for each command in the program.
Command Conventions
Some basic ideas on how commands work and are used.
Grid Commands
Commands to control grid generation and refinement.
Post Processing Commands
Commands to analyze data.
Application Specific Commands
Commands to solve systems of equations, deposit materials, and more!
Other Commands
Miscellaneous commands that aren't really categorizable. There are many useful commands here!
Development
- New Developments - A brief list of the new enhancements since the last release.
- Bugs - A list of current FLOOXS Bugs that need action
- "To Do" List - Needed code enhancements for specific actions
Installation
- Installation Directions - Installation help and notes - created as I did a clean install on a linux system. Your mileage may vary.
Copyright and Redistribution
This software and manual is copyrighted by the Mark Law, University of Florida Electrical and Computer Engineering department. It is intended for internal educational and research and development purposes only. Any use of any part of this software in any commercial package needs to be negotiated separately. Several of the implant models are copyrighted by Al Tasch from The University of Texas at Austin.
The UMFPACK package is copyrighted by Tim Davis, University of Florida, Computer and Information Sciences Department. (davis@cis.ufl.edu). Please contact Tim directly about redistribution of the UMFPACK software.
The tcl/tk package is in the public domain, and was developed by John Ousterhout at the University of California Berkeley.
Various included linear algebra packages are also public domain.
Getting started with Wiki
Consult the User's Guide for information on using the wiki software.