Help CircuitSafari Manual

<!
DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>CircuitSafari Help</title>
<meta name="viewport" content="initial-scale=1">
<style>
.screenshot {
width: 600px;
}
.toolbarButton {
border: 5px solid gray;
width: 40px;
}
body {
font-family: "Verdana", "Arial", "sans serif";
}
div.heading {
text-align: center;
}
th {
text-align: left;
background-color: #f2f2f2;
}
tr:nth-child(odd) {
background-color: #f2f2f2;
}
tr:hover {
background-color: #ddd;
}
table {
border-collapse: collapse;
width: 100%;
}
font {
font-size: 1.5em;
}
</style>
</head>
<body>
<div class="heading"><h4>CircuitSafari Version 2.1.5<br />
© 2018-2022 Logipipe, LLC</h4>
</div>
<div class="heading"><h4>Contents</h4></div>
<ul>
<li><a href="#introduction">Introduction</a></li>
<li><a href="#program_setup">Program setup</a></li>
<li><a href="#schematic_capture">Schematic capture</a></li>
<li><a href="#managing_google_drive_files">Managing Google
Drive™ files</a></li>
<li><a href="#simulator">Simulator</a></li>
<li><a href="#subcircuits">Subcircuits</a></li>
<li><a href="#digital_logic">Digital Logic</a></li>
<li><a href="#arithmetic_expressions">Arithmetic
expressions</a></li>
<li><a href="#kicad_integration">KiCad integration</a></li>
<li><a href="#archive_files">Archive files</a></li>
<li><a href="#privacy_policy">Privacy policy</a></li>
<li><a href="#terms_of_use">Terms of use</a></li>
<li><a href="#licensed_third_party_software">Licensed third
party software</a></li>
<li><a
href="https://www.logipipe.com/circuitsafari">CircuitSafari
Website</a></li>
<li><a
href="https://www.youtube.com/channel/UCbO8lu7fZMvt1tJLO0dN8sQ">Logipip
e, LLC YouTube Channel</a></li>
</ul>
<p>
Google Drive is a trademark of Google Inc.
Use of this trademark is subject to Google Permissions.
</p>
<a class="anchor" id="introduction"></a>
<div class="heading"><h4>Introduction</h4></div>
<p>
CircuitSafari is software for interactive electronic schematic
capture and mixed signal
simulation with a touchscreen interface.
Features include:</p>
<ul>
<li>AC, DC and transient circuit analysis</li>
<li>unlimited workspace, limited only by the amount of memory on
your device</li>
<li>schematics spanning an unlimited number of pages</li>
<li>hierarchical schematics with unlimited subcircuit depth</li>
<li>full autorouting for schematic capture</li>
<li>cut and paste parts of circuits between different
schematics</li>
<li>subcircuit specification through schematic capture or a spice
net list</li>
<li>subcircuit formal arguments</li>
<li>support for expressions in component parameters</li>
<li>import standard spice models and subcircuits from third party
vendors</li>
<li>develop a custom library of components for use in future
simulations</li>
<li>generate professional looking pdf files and printouts of
schematics</li>
<li>continuous autosaving in the background as the circuit is being
edited</li>
<li>Google Drive integration</li>
<li>share circuits through email or Google Drive</li>
<li>schematic capture and circuit simulation without a network
connection</li>
<li>multiple channel oscilloscope with linear and logarithmic views
incuding FFT
(pro version only for circuits with more than 50 nodes)</li>
<li>interactive component adjustment and display of simulation
results as the simulation
is in progress</li>
<li>visualization of simulation progress on simulated LEDs, seven
segment displays,
bar displays and dot matrix displays</li>
<li>interact with your circuit through simulated switches and
potentiometers</li>
<li>learn electronics and program use through included example
circuits</li>
<li>export a net list that can be imported directly into KiCad
Pcbnew for PC board layout</li>
</ul>
<a class="anchor" id="program_setup"></a>
<div class="heading"><h4>Program Setup</h4></div>
<p>
For a quick demo, select an example by hitting "File->Example Root
Circuits" and hit the play button.
</p>
<p>
Some examples
require downloading spice models from a manufacturer's website and
copying them to the project
directory. These examples will display an error message indicating that
some files failed to
load when the example is selected. Hit "View->Log" to discover the
reference designator
of the part whose file failed to load. Select that part on the
schematic then select
"Push" from the context menu for more information on where to get that
spice model from.
See the section "Managing Google Drive Files" for information on how to
copy these spice
models to the project directory.
</p>
There are few examples that have convergence issues when "Current Dot
Visibility" is not
turned off in a ".current_dots" SPICE directive.
To speed simulation and avoid these convergence errors, keep this
feature turned off for the example
at the expense of not being able to visualize current flow on the
schematic.
<p>
Files created with the program are saved to Google Drive under the
account specified by hitting
"Google Drive->Select Account". Before files can be stored on Google
Drive, a project directory
on Google Drive must be specified by hitting "Google Drive->Select
Directory->Select Project Directory".
CircuitSafari only sees files and directories on Google Drive that were
created with the program.
</p>
<p>
Some demos use symbols from KiCad symbol and footprint libraries, which
are available at
<a href="https://www.kicad.org/libraries/download/">
https://www.kicad.org/libraries/download/</a>.
CircuitSafari is able to load both KiCad 5 and KiCad 6 libraries stored
as either ".zip" or ".7z"
archives without needing to manually decompress them first. The
libraries you should download for
CircuitSafari are kicad-symbols-master.zip and
kicad-footprints-master.zip. To specify which libraries
to load, hit "File->Pick Symbol Libraries" and "File->Pick Footprint
Libraries".
</p>
<p>
Some components specify a file that is used by the component. When
searching for a file
to load for the component, CircuitSafari
does a case insensitive search for the file, first in the CircuitSafari
Project Directory, then
in the Library Directory and finally in the local directory of examples
that came with CircuitSafari.
<a class="anchor" id="schematic_capture"></a>
<div class="heading"><h4>Schematic Capture</h4></div>
<p>To place a new component on the drawing area, scroll through the
list of primitive
components by dragging the list until the desired component
is visible.
Then single tap on this component. This will cause the
component that was tapped to be
highlighted. Finally single tap in the drawing area where you
wish to place
the component.</p>
<p>To make a connection, single tap on a pin or wire to select it

and then single tap on
another pin or wire. Connections can also be made by giving two
wires the same label.
This is done by connecting a wire to a "LABEL" component. Note
that placing one pin on top
of another pin does not create a connection in CircuitSafari.
A wire must connect to
a pin in order to make a connection.</p>
<p>To disconnect a wire, tap on a wire to select it. To

disconnect just a segment of a wire,
tap on that segment a second time. Then hit the delete
button.</p>
<p>To move components, specify the components to be moved by

single tapping on
components to select them. Then drag the components to be
moved to a new
area on the screen. Finally tap on an unused portion of the
schematic to
unselect the selected components.</p>
<p>A rectangular region of components can be selected by hitting

"Edit->Select Region" and then
dragging across the diagonal of the rectangular region.</p>
<p>The menu button serves a dual purpose, depending on whether or not a

component is selected.
If a component is selected, pressing the menu button will display a
context menu for
the selected components.</p>
<p>Selected components can be moved to a different

page or schematic by selecting
cut from the context menu. Then long press on an unused area
of the page
where the parts should be placed and select paste from the
context menu.</p>
<p>To duplicate selected components, select copy
from the context menu. Then paste the copied components on
an unused portion of
the schematic.</p>
<p>To rotate selected parts counterclockwise, tap the rotate

counterclockwise
button. To flip selected parts horizontally, tap the flip
horizontal button.
To flip selected parts vertically, double tap the flip
horizontal button.</p>
<p>Component attributes can be edited by double tapping on a

component. A
control panel with a list of attributes for the component
will appear.
Single tap on an attribute to adjust its value. A knob or a
switch
will appear depending on the type of the attribute. A knob
can be turned
by dragging a spiral from the center of the knob. A switch
can be toggled
by single tapping on the switch. Long press on an attribute
or its control
to enter a new value for the attribute. Some attributes have
a menu associated with them.
To display the menu, single tap on the knob. Multiple
components of the same
type can be selected and edited simultaneously.</p>
<p>A spice directive can be specified by placing a text component

with its
isSpiceDirective attribute set anywhere on the
schematic.</p>
<p>Components with a model name attribute have some of their

attributes
specified through a corresponding .model spice directive. If
a file name
is specified in the component's File attribute, the
specified file is
searched for the .model spice directive.
Attribute values that can be specified on a .model statement
for components with the same model name track each other
when the
attribute value is changed. The exception
to this rule is when a model name is not specified.
Attribute values from the .model
spice directive are copied to the components that use that
model when the
simulation is started.</p>
<p>To save a schematic to a new file, hit "Google Drive->Save

As". To save
to the same file, hit "Google Drive->Save". The schematic
can later be retrieved
with "Google Drive->Open". Files can be saved even when
there is no
network connection. To retrieve a file on a different
device, hit "Google Drive->Synchronize"
on the device where the file exists. After synchronization
is complete, hit
"Google Drive->Synchronize" on the other device. Files
synchronized with Google Drive
remain on Google Drive even if the program is
uninstalled.</p>
<a class="anchor" id="managing_google_drive_files"></a>
<div class="heading"><h4>Managing Google Drive Files</h4></div>
<p>Since CircuitSafari only has the ability to see files in

Google Drive that it created,
one cannot simply upload a file to Google Drive using
Google's Google Drive app,
synchronize the Google Drive files with CircuitSafari by
hitting
"Google Drive->Synchronize", and expect the file to be
visible to CircuitSafari.
CircuitSafari has built in features for managing Google
Drive files for this purpose.</p>
<p>CircuitSafari's built in text editor can be used to upload a

file to Google Drive
("Edit->Edit Text File"). To do so, hit "File->Open" from
within the text editor
and select the file to upload to Google Drive. Next hit the
save as icon in the text
editor, enter the desired file name for the file in the
Google Drive project
directory and hit OK. If you wish the file to appear on
Google's Google Drive server,
hit "Google Drive->Synchronize". This works for all file
types, not just text files.</p>
<p>If the desired file is hidden in a ZIP file, hit "Google

Drive->Extract->Extract ZIP File"
to place the contents of the ZIP file into a directory in
the project directory. One
can then move the desired file in this directory to the
desired location by hitting
"Google Drive->File Manager".</p>
<p>To move files from within CircuitSafari's Google Drive file

manager, select the files
to move by single tapping on them. A directory can be
selected by long pressing
on the directory. Next, long press on one of the selected
files to bring up the
file manager context menu. Select "Move to..." to move the
selected files to the
desired location.</p>
<p>It is not necessary to log into a Google account to use
CircuitSafari. There is a special
section in CircuitSafari's Google Drive cache when no account is
selected. These files
can't be synchronized with Google's Google Drive server, but zip
archives of files in this
file system can be exported using CircuitSafari's Google Drive
file manager.</p>
<a class="anchor" id="simulator"></a>

<div class="heading"><h4>Simulator</h4></div>
<p>Once a schematic has been entered, it can be simulated by

hitting the play button. While
the simulation is running, the pause button takes the place
of the play button and a rewind
button appears. Tap the pause button to pause the simulator.
Double tap the pause
button to single step the simulator. Hit the play button to
resume the simulator.
Hit the rewind button to stop the simulator.</p>
<p>A .tran spice directive can be used to specify the simulation
time step and simulation
run time. To select an AC analysis, place a .ac spice
directive on the schematic.
To specify a DC analysis place a .dc spice directive on the
schematic. A series of
simulations can be run while stepping an attribute value by
using a .step spice directive.
A simulation can be repeated automatically by using a .tune
spice directive.</p>
<p>There are four different simulator implementations to choose
from, which is
selectable with a ".options implementation" spice directive.
Spice3f5 is the classic spice simulator from the University
of California
running natively with Logipipe extensions written in Java
that add
logic components and expressions. The Logipipe simulator
implemention is written entirely in Java but uses OpenBLAS
running natively
for matrix manipulation. It allows interactively adjusting
all component attributes
while the simulation is in progress.
The ngspice implementation is ngspice release 35 with
Logipipe extensions for digital
logic. The XSPICE implementation is ngspice release 35 with
XSPICE extensions
for digital logic.</p>
<p>Simulation results are displayed on meter components and an
oscilloscope.
There are voltmeters, ammeters, ohmmeters, wattmeters,
frequency meters and
distortion meters.
Any meter can be connected to the oscilloscope by changing
its "Scope Channel"
attribute to the oscilloscope channel you wish to connect it
to. There is also
an oscilloscope probe that is a voltmeter with its negative
lead connected to
ground. A bus can be connected to the oscilloscope by
selecting the labels that
make up the bus and then setting their "Scope Channel"
attribute to the channel of the
oscilloscope to connect the bus to. Oscilloscope channel
settings are adjustable
in a scope probe's control panel.</p>
<p>To quickly view the voltage of a net on the oscilloscope, select the
net, then tap the "eye"
button in the toolbar.
</p>
<p>To be able to quickly view the current flowing into a pin on the
oscilloscope,
"Show current dots" must be enabled in "File->Settings" or the
setting must be overriden with
a ".current_dots" SPICE directive with its "Current Dot
Visibility" attribute turned on.
To view the current if this option
is enabled, select a single part on the schematic, tap on one of
the part's pins,
then tap the "eye" button in the toolbar.</p>
<p>Both oscilloscope cursors can be placed at the same position
by tapping on the bottom of the ocilloscope window. A cursor
can be dragged
to any other position by dragging the cursor handle.
For finer cursor control, zoom in the oscilloscope by
reverse pinching the oscilloscope.</p>
<a class="anchor" id="subcircuits"></a>

<div class="heading"><h4>Subcircuits</h4></div>
<p>The only difference between a root circuit and

a subcircuit is that a subcircuit has pins. Each subcircuit
specification resides in
its own file.</p>
<p>The icon for a subcircuit reference looks like an 8 pin DIP IC in

the part menu.
If "Custom Subcircuit" reference is placed on a schematic, double
tap on the subcircuit
to display a control panel for the subcircuit reference. Single
tap on the knob
for the "File" attribute to display a menu of files. Select the
file of the subcircuit
specification you wish to reference. The pins in the subcircuit
specification
will automatically appear in the subcircuit reference.</p>
<p>The symbol for a subcircuit is automatically generated from

parameters specified
in the control panels of a subcircuit's pins. Alternatively, a
subcircuit's
symbol can be selected from symbols specified in
a <a href="http://kicad-pcb.org">KiCad</a> compatible symbol
library by changing
a subcircuit component's symbol parameter. The KiCad
libraries to import are specified by hitting "File->Pick Symbol
Libraries".</p>
<p>To navigate to a subcircuit specification from a referencing

schematic, highlight
the subcircuit reference by single tapping on it
and select "Push" from the context menu. To navigate back
to the referencing schematic, long press on an unused portion of
a subcircuit's
schematic and select "Pop" from the context menu.</p>
<p>To define your own subcircuit, place pins on the schematic for the
subcircuit
specification. The icon for a pin looks like an arrow in the part
menu. To
visualize where the pins would appear on a subcircuit reference,
place
a subcircuit reference on the subcircuit schematic and change its
isRecursive
attribute to true.</p>
<p>To change a pin's attributes, double tap on a pin. The values of the
pin number
and pin name attributes appear in the subcircuit reference. Each
pin in a
subcircuit must have a unique pin number. To change where the pin
appears
in a subcircuit reference, change a pin's orientation and
location attributes.</p>
<p>Formal arguments can be passed to a subcircuit by placing a .formal

spice
directive in a subcircuit's schematic. Double, string and boolean
data types can be passed.
A formal double argument that maps to a boolean attribute value
on a component
in the subcircuit is shown as a switch on the control panel for a
referencing
subcircuit component.</p>
<p>To be able to reference the subcircuit specification from another

schematic,
save the subcircuit specification in either the project directory
or library
directory on Google Drive.</p>
<p>A subcircuit may be defined by an unencrypted PSpice compatible

subcircuit specification
that was downloaded from a manufacturer's website. Some LTspice
subcircuit
specifications that are available in the <a
href="https://groups.io/g/LTspice">
LTspice user's group</a> work as well. So do ngspice
compatible subcircuit
specifications.
To reference such a subcircuit,
place the file containing the spice subcircuit code into either
the project directory
or library directory in Google Drive.
Then change the file attribute of a subcircuit reference to the
file
containing the PSpice compatible subcircuit specification. Next
change the "Model Name"
attribute in the subcircuit reference to the desired subcircuit
in the PSpice file.
It may be necessary to automatically translate PSpice or LTspice
code to Ngspice code by changing
the subcircuit reference's "Reverse Engineer" attribute to on.
</p>
<a class="anchor" id="digital_logic"></a>

<div class="heading"><h4>Digital Logic</h4></div>
<p>Digital logic elements need a power and ground connection.

They are made by naming nets
on the schematic. By default, power is tied to a net called
"VCC" and ground is tied
to a net called "0" (the ground symbol). To use the
defaults, you must label a net
on the schematic "VCC" with a "LABEL" component.</p>
<p>The XSPICE implementation implements propagation delays for
digital logic,
while the other three implementations have logic propagation
delays of 0 by default.
The power and ground connections for a logic element must be
tied to nodes with
a resistance to ground of 0 ohms. This is done by tying the
power net directly to
a battery with the other lead of the battery tied to
ground.</p>
<p>There is an optional implementation of logic gates for all
four simulator implementations
that implements propagation delays and does not have the 0
ohm to ground restriction on its
power and ground connections. The optional implementation
also exports spice code that is compatible
with other simulators. The disadvantage of the optional
implementation is that
it has more nodes and a slower simulation speed than the
default implementation.
To enable the optional implementation, change a gate's "Has
Propagation Delay"
attribute to true. </p>
<p>The default logic gate implementation requires the use of the
provided flip flop components
for flip flops, while flip flops in the implementation of
logic gates with
propagation delays are implemented directly with gates, but
for the logic state of a
flip flop to settle, the gates must have unequal propagation
delays.</p>
<a class="anchor" id="arithmetic_expressions"></a>

<div class="heading"><h4>Arithmetic Expressions</h4></div>
<p>Attribute values can be expressions. To assign an expression
to an attribute,
long press on the switch or knob.</p>
<div>Predefined values</div>
<table>
<tr><th>Identifier</th>
<th>Description</th></tr>
<tr><td>hertz</td><td>the simulation frequency
when performing an
AC analysis</td></tr>
<tr><td>infinity</td><td>∞</td></tr>
<tr><td>pi</td><td>3.14...</td></tr>
<tr><td>temper</td><td>the simulation
temperature in degrees Celsius, as
specified with the ".options temp" spice
directive</td></tr>
<tr><td>time</td><td>the simulation elapsed
time in virtual seconds
when performing a transient analysis</td></tr>
</table>
<br />
<div>Operators in order of precedence</div>
<table>
<tr><th>Operators</th>
<th>Description</th>
<th>Associativity</th></tr>
<tr><td>� - �</td><td>unary plus, minus and
not</td><td>left</td></tr>
<tr><td>**</td><td>x ** y is equivalent to raise
abs(x) to the y power</td><td>left</td></tr>
<tr><td>* /</td><td>multiply and
divide</td><td>left</td></tr>
<tr><td>� -</td><td>add and
subtract</td><td>left</td></tr>
<tr><td>< <= == != >=
></td><td>relational operators</td><td>left</td></tr>
<tr><td>& |</td><td>boolean and and
or</td><td>left</td></tr>
<tr><td>^</td><td>boolean exclusive
or</td><td>left</td></tr>
<tr><td>? :</td><td>ternary conditional
operator</td><td>right</td></tr>
</table>
<br />
<div>Predefined functions</div>
<table>
<tr><th>Functions</th>
<th>Description</th></tr>
<tr><td>abs(x)</td><td>absolute value</td></tr>
<tr><td>absdelay(x, t)</td><td>alternate form
of delay(x, t)</td></tr>
<tr><td>atan2(y, x)</td><td>four quadrant arc
tangent with angle in radians</td></tr>
<tr><td>ceil(x)</td><td>nearest integer >=
x</td></tr>
<tr><td>ddt(x)</td><td>time derivative of
x</td></tr>
<tr><td>delay(x, t)</td><td>x delayed t
seconds. t is evaluated before the simulation starts.</td></tr>
<tr><td>exp(x)</td><td>e ** x</td></tr>
<tr><td>floor(x)</td><td>nearest integer <=
x</td></tr>
<tr><td>gauss(x, deviation, sigma)</td><td>a
gaussian distributed pseudorandom value with a mean of x
and a standard deviation of deviation /
sigma</td></tr>
<tr><td>i(refdes)</td><td>the current flowing
from pin 1 to pin 2 of two pin part with reference designator
refdes</td></tr>
<tr><td>i(refdes, pinNumber)</td><td>the
current flowing into pin pinNumber of part with reference designator
refdes</td></tr>
<tr><td>idt(x[, ic])</td><td>alternate form of
sdt(x[, ic])</td></tr>
<tr><td>im(x)</td><td>the imaginary part of
complex number x</td></tr>
<tr><td>int(x)</td><td>convert x to an integer,
truncating toward 0</td></tr>
<tr><td>limit(x, y, z)</td><td>x < y ? y : (x
> z ? z : x)</td></tr>
<tr><td>ln(x) log(x)</td><td>natural
logarithm</td></tr>
<tr><td>log10(x)</td><td>base 10
logarithm</td></tr>
<tr><td>mag(x)</td><td>the magnitude of complex
number x</td></tr>
<tr><td>max(x, y)</td><td>x > y ? x :
y</td></tr>
<tr><td>min(x, y)</td><td>x < y ? x :
y</td></tr>
<tr><td>re(x)</td><td>the real part of complex
number x</td></tr>
<tr><td>round(x)</td><td>nearest
integer</td></tr>
<tr><td>sdt(x[, ic])</td><td>time integral of x
with optional initial condition ic</td></tr>
<tr><td>sin(x) cos(x) tan(x) asin(x) acos(x)
atan(x)</td><td>trigonometric functions with angle in radians</td></tr>
<tr><td>sinh(x) cosh(x) tanh(x) asinh(x)
acosh(x) atanh(x)</td><td>hyperbolic functions</td></tr>
<tr><td>sum(expression, k, initialValue,
finalValue)</td>
<td>The sum of the terms generated by
substituting the variable specified
by k in expression with an integer in
the
sequence of consecutive integers
between initial value and final value inclusive.
This function can only be used in the
specification of a Laplace transfer function.</td></tr>
<tr><td>product(expression, k, initialValue,
finalValue)</td>
<td>The product of the factors generated by
substituting the variable specified
by k in expression with an integer in
the
sequence of consecutive integers
between initial value and final value inclusive.
This function can only be used in the
specification of a Laplace transfer function.
</td></tr>
<tr><td>ph(x)</td><td>the phase of complex
number x in degrees</td></tr>
<tr><td>pwr(x, y)</td><td>abs(x) ** y</td></tr>
<tr><td>pwrs(x, y)</td><td>(x < 0 ? -1 : 1) *
(abs(x) ** y)</td></tr>
<tr><td>sgn(x)</td><td>x > 0 ? 1 : (x < 0
? -1 : 0)</td></tr>
<tr><td>sqr(x)</td><td>x ** 2</td></tr>
<tr><td>sqrt(x)</td><td>square root</td></tr>
<tr><td>table(x, x0, y0, x1, y1, ..., xn,
yn)</td>
<td>piecewise linear interpolation, y0 if x
< x0, yn if x > xn</td></tr>
<tr><td>u(x)</td><td>x > 0 ? 1 : (x < 0 ? 0 :
0.5)</td></tr>
<tr><td>uramp(x)</td><td>x > 0 ? x : 0</td></tr>
<tr><td>unif(x, tolerance)</td><td>a uniformly
distributed pseudorandom value between x * (1 - tolerance) inclusive
and x * (1 � tolerance)
exclusive</td></tr>
<tr><td>v(label)</td><td>the voltage at node
label</td></tr>
<tr><td>v(label1, label2)</td><td>the voltage
between nodes label1 and label2</td></tr>
</table>
<p>New functions can be defined by placing .func
spice directives on the schematic. An
example of a .func spice directive is ".func f(x) {x
* x}". Defining a .func spice
directive requires turning the "Spice Gui"
attribute for that spice directive off.</p>
<a class="anchor" id="kicad_integration"></a>
<div class="heading"><h4>KiCad Integration</h4></div>
<p>
Schematics created with CircuitSafari can be exported to KiCad Eeschema
for further
schematic capture or circuit simulation and to KiCad Pcbnew for PC
board layout.
</p>
<p>
To export to Eeschema, three files must be exported by hitting
"File->Export->Export KiCad Schematic",
"File->Export->Export KiCad Library" and "File->Export->Export SPICE
Library".
Schematics exported to Eeschema are limited to one page.
</p>
<p>
Even though schematics exported to Eeschema can be exported to Pcbnew
from Eeschema, it is preferred
to export directly to Pcbnew by hitting "File->Export->Export KiCad Net
List". The advantage is that
schematics exported directly to Pcbnew are not limited to one page,
only one file needs to be exported, and
fewer steps are required before the net list reaches Pcbnew.
</p>
<a class="anchor" id="archive_files"></a>

<div class="heading"><h4>Archive files</h4></div>
<p>
A CircuitSafari archive file has the ".lca" file extension. This file
typically includes all the files needed to simulate a circuit. This
makes it
easy to share complete circuits with other people. When an archive file
is opened,
all the files included in the archive are loaded into CircuitSafari.
Files can be
saved to an archive by hitting "File->Save Archive". They can be loaded
by hitting "File->Open".
Files in an archive can be manipulated by hitting "Google
Drive->Extract->Extract LCA File".
</p>
<p>
More details about CircuitSafari's file formats are available
<a
href="https://www.logipipe.com/circuitsafari/file_types.html">here</a>.
</p>
<a class="anchor" id="privacy_policy"></a>
<div class="heading"><h4>Privacy Policy</h4></div>
<p>
Click <a
href="https://www.logipipe.com/circuitsafari/privacy.html">
here</a> to view the CircuitSafari privacy policy.
</p>
<a class="anchor" id="terms_of_use"></a>
<div class="heading"><h4>Terms of Use</h4></div>
<p>
Click <a
href="https://www.logipipe.com/circuitsafari/TermsOfUse.html">
here</a> to view the CircuitSafari terms of use.
</p>
<a class="anchor" id="licensed_third_party_software"></a>
<div class="heading"><h4>Licensed Third Party Software</h4></div>
<ul><li>
<p><b>This software includes Spice3f5 and ngspice release 35,
subject to the “modified” BSD license,
requiring the following notice:</b></p>
<p>Copyright (c) 1985-1991 The Regents of the University of
California.
All rights reserved.</p>
<p>Permission is hereby granted, without written agreement and

without license
or royalty fees, to use, copy, modify, and distribute this
software and its
documentation for any purpose, provided that the above
copyright notice and
the following two paragraphs appear in all copies of this
software.</p>
<p>IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY

PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT
OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE
UNIVERSITY OF
CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.</p>
<p>THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY
WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED
HEREUNDER IS ON AN
"AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
OBLIGATION TO PROVIDE
MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
MODIFICATIONS.</p>
</li></ul>
<ul><li>
<p><b>Spice3f5 and ngspice release 35 include Sparse1.3, requiring
the following notice:</b></p>
<p>Copyright (c) 1985,86,87,88,89,90 by Kenneth S. Kundert and the
University of California.</p>
<p>
Permission to use, copy, modify, and distribute this software and
its
documentation for any purpose and without fee is hereby granted,
provided
that the above copyright notice appear in all copies and supporting
documentation and that the authors and the University of California
are properly credited. The authors and the University of
California
make no representations as to the suitability of this software for
any purpose. It is provided `as is', without express or implied
warranty.
</li>
<li>
<p><b>This software includes BSIM device models, developed by the
UC Berkeley
BSIM Research Group, requiring the following notice:</b></p>
<p>The terms under which the software is provided are as the
following.</p>
<p>Software is distributed as is, completely without warranty or

service
support. The University of California and its employees are not
liable
for the condition or performance of the software.</p>
<p>The University owns the copyright but shall not be liable for
any
infringement of copyright or other proprietary rights brought by
third
parties against the users of the software.</p>
<p>The University of California hereby disclaims all implied

warranties.</p>
<p>The University of California grants the users the right to

modify, copy,
and redistribute the software and documentation, both within the
user's
organization and externally, subject to the following
restrictions:</p>
<ol>
<li>The users agree not to charge for the University of
California code
itself but may charge for additions, extensions, or
support.</li>
<li>In any product based on the software, the users agree to

acknowledge
the UC Berkeley BSIM Research Group that developed the
software. This
acknowledgment shall appear in the product
documentation.</li>
<li>The users agree to obey all U.S. Government restrictions

governing
redistribution or export of the software.</li>
<li>The users agree to reproduce any copyright notice which

appears on
the software on any copy or modification of such made
available
to others.</li>
</ol>
<p>Chenming Hu, and Weidong Liu<br />

Mar. 2000</p>
</li>
<li>
<p><b>This software includes the HISIM device model, owned by
Hiroshima University
and the STARC organization, requiring the following
notice:</b></p>
<p>Software is distributed as is, completely without
warranty or service
support. Hiroshima University or STARC and its employees are
not liable
for the condition or performance of the software.</p>
<p>Hiroshima University and STARC own the copyright and

grant users a perpetual,
irrevocable, worldwide, non-exclusive, royalty-free license
with respect
to the software as set forth below.</p>
<p>Hiroshima University and STARC hereby disclaim all

implied warranties.</p>
<p>Hiroshima University and STARC grant the users the right

to modify, copy,
and redistribute the software and documentation, both within
the user's
organization and externally, subject to the following
restrictions</p>
<ol>
<li>The users agree not to charge for Hiroshima
University and STARC code
itself but may charge for additions,
extensions, or support.</li>
<li>In any product based on the software, the
users agree to acknowledge
Hiroshima University and STARC that developed
the software. This
acknowledgment shall appear in the product
documentation.</li>
<li>The users agree to reproduce any copyright

notice which appears on
the software on any copy or modification of such
made available
to others.</li>
</ol>
</li>
<li>
<p><b>This software includes the HISIM_HV device model, owned by
and the STARC organization, requiring the following
notice:</b></p>
<p>Hiroshima University and/or Semiconductor Technology Academic
Research
Center ("STARC") grants to Licensee a worldwide, royalty-free,
sub-licensable, retroactive, perpetual, irrevocable license to
make,
have made, offer to sell, sell, import, export, use, copy,
redistribute,
perform, display and incorporate HiSIM_HV intellectual property
(the
"License") subject to the conditions set forth below.</p>
<p>This License includes rights to use and modify copyrighted
material
for any purpose if the copyright is acknowledged as well as the
use of
related patents which STARC owns, has applied for or will apply
for
in connection with HiSIM_HV intellectual property for the purpose
of
implementing and using he HiSIM_HV intellectual property in
connection
with the standard. This license applies to all past and future
versions
of HiSIM_HV.</p>
<ol>
<li>HiSIM_HV intellectual property is offered "as is"
without any warranty,
explicit or implied, or service support. Hiroshima
University, STARC,
its University staff and employees assume no liability for
the quality
and performance of HiSIM_HV intellectual
property.</li>
<li>As the owner of the HiSIM_HV intellectual property, and

all other
related rights, Hiroshima University and/or STARC grant the
License
as set forth above.</li>
<li>A Licensee may not charge an end user a fee for the
HiSIM_HV source
code, which Hiroshima University and STARC own, by itself,
however,
a Licensee may charge an end user a fee for alterations or
additions
to the HiSIM_HV source code or for maintenance
service.</li>
<li>A Licensee of HiSIM_HV intellectual property agrees that

Hiroshima
University and STARC are the developers of HiSIM_HV in all
products
containing HiSIM_HV and the alteration thereof (subject to
Licensee's
ownership of the alterations).
If future versions of HiSIM_HV incorporate elements of other
CMC models
the copyrights of those elements remains with the original
developers.
For this purpose the copyright notice as shown below
shall be used.
<p>"The HiSIM_HV source code, and all copyrights, trade

secrets or other
intellectual property rights in and to the source code, is
owned
by Hiroshima University and/or STARC."</p></li>
<li>A Licensee of HiSIM_HV intellectual property will comply

with the
export obligations pertaining to the export of the HiSIM_HV
intellectual
property.</li>
<li>By using HiSIM_HV intellectual property owned by

and/or STARC, Licensee agrees not to prosecute any patents
or patent
held by Licensee that are required for implementation of
HiSIM_HV against
any party who is infringing those patents solely by
implementing and/or
using the HiSIM_HV standard.</li>
</ol>
<p>Toshimasa Asahara, President, Hiroshima University<br />
Mitiko Miura-Mattausch, Professor, Hiroshima University<br />
Katsuhiro Shimohigashi, President&CEO, STARC<br />
June. 2008 (revised in June 2011)</p>
</li>
<li>
<p><b>This software includes the STAG computer model, requiring
the following notice:</b></p>
<p>Licence Agreement (STAG) from DERA</p>
<ol>
<li>The STAG Computer Model is subject to Copyright owned by
the United Kingdom
Secretary of State for Defence acting through the Defence
Evaluation and Research Agency
(DERA). It is made available to licensee (hereinafter
LICENSEE) on the following conditions:-</li>
<li>Downloading the STAG Model deems acceptance of the terms

of the licence.</li>
<li>DERA grants to LICENSEE a royalty free non-exclusive

licence to use the furnished STAG
Model. LICENSEE is permitted to copy, distribute, and
transfer the STAG Model to
customers for their royalty free use on the same licence
terms.</li>
<li>LICENSEE acknowledges that STAG is a research tool still

in the development stage, that
it is being supplied "as is", without any accompanying
services or improvements from
DERA.</li>
<li>LICENSEE acknowledges that STAG is a Model developed by

the Department of
Electronics and Computer Science at the University of
Southampton (UOS), England, and is
incorporated within SPICE 3f5, a program developed by the
Department of Electrical
Engineering and Computer Science at the University of
California, Berkeley, California
(UCB). As such, LICENSEE acknowledges that in addition to
the rights licensed by DERA,
UCB itself imposes restrictions on use, copying, and
distribution of the SPICE 3f5 program
and its derivatives.</li>
<li>LICENSEE undertakes to obtain any separate licence

required for the use of SPICE 3f5
from UCB.</li>
<li>DERA make no representations or warranties, express or

implied. DERA shall not be held
liable for any liability nor for any direct, indirect, or
consequential damages with respect to
any claim by LICENSEE or any third party on account of or
arising from this Agreement or
use of STAG.</li>
<li>Title to copyright of all portions of STAG developed at

UOS and/or DERA together with
associated documentation shall at all times remain with
DERA, and LICENSEE agrees to
preserve same. LICENSEE agrees to ensure that this
information and appropriate copyright
notice is reproduced with any copies of STAG or any modified
versions derived from it.</li>
<li>This agreement shall be construed, interpreted, and

applied in accordance with the laws
of England.</li>
</ol>
<p>for DERA by:</p>
<p>J B EDWARDS<br/>
IPD5A<br />
10 NOV 1997</p>
<p>Intellectual Property Department<br />

Defence Evaluation and Research Agency<br />
St Andrews Road<br />
Malvern<br />
WR14 3PS<br />
United Kingdom</p>
<p>phone: � - 1684 - 894234<br />

fax: � - 1684 - 894146</p>
</li>
<li>
<p><b>This software includes XSPICE, which is in the public
domain.</b></p>
<p>THE SOFTWARE PROGRAMS BELOW ARE IN THE PUBLIC DOMAIN AND ARE
PROVIDED FREE OF
ANY CHARGE. THE GEORGIA TECH RESEARCH CORPORATION, THE
GEORGIA INSTITUTE OF
TECHNOLOGY, AND/OR OTHER PARTIES PROVIDE THIS SOFTWARE "AS
IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE
ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH THE USER.
SHOULD THE PROGRAM PROVE DEFECTIVE, THE USER ASSUMES THE
ENTIRE COST OF ALL
NECESSARY SERVICING, REPAIR OR CORRECTION. IN NO EVENT WILL
THE GEORGIA TECH
RESEARCH CORPORATION, THE GEORGIA INSTITUTE OF TECHNOLOGY,
AND/OR OTHER PARTIES
PROVIDING THE PROGRAMS BELOW BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO
LOSS OF DATA OR DATA
BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR
THIRD PARTIES OR A
FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS).
</p>
</li>
<li>
<p><b>This software includes OpenBLAS, covered by the following
copyright:</b></p>
<p>Copyright (c) 2011-2014, The OpenBLAS Project<br />

All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or

without
modification, are permitted provided that the following
conditions are
met:</p>
<ol>
<li>Redistributions of source code must retain the above
copyright
notice, this list of conditions and the following
disclaimer.</li>
<li>Redistributions in binary form must reproduce the above

copyright
notice, this list of conditions and the following
disclaimer in
the documentation and/or other materials provided with the
distribution.</li>
<li>Neither the name of the OpenBLAS project nor the names of

its contributors may be used to endorse or promote products
derived from this software without specific prior written
permission.</li>
</ol>
<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
</p>
</li>
<li>
<p><b>This software includes KISS FFT, requiring the following
notice:</b></p>
<p>Copyright (c) 2003-2010 Mark Borgerding</p>
<p>All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without

modification,
are permitted provided that the following conditions are
met:</p>
<ol>
<li>Redistributions of source code must retain the above copyright
notice,
this list of conditions and the following disclaimer.</li>
<li>Redistributions in binary form must reproduce the above
copyright notice,
this list of conditions and the following disclaimer in the
documentation
and/or other materials provided with the distribution.</li>
<li>Neither the author nor the names of any contributors may be
used to endorse
or promote products derived from this software without specific
prior written
permission.</li>
</ol>
<p>
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
</p>
</li>
<li>
<p><b>This software includes UsbSerial version 6.1.0,
which is available at <a
href="https://github.com/felHR85/UsbSerial">
https://github.com/felHR85/UsbSerial</a>,
subject to the following license:</b></p>
<p>The MIT License (MIT)</p>
<p>Copyright (c) 2014 Felipe Herranz</p>
<p>
Permission is hereby granted, free of charge, to any person
obtaining a copy
of this software and associated documentation files (the
"Software"), to deal
in the Software without restriction, including without
limitation the rights
to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is
furnished to do so, subject to the following conditions:
</p>
<p>
The above copyright notice and this permission notice shall
be included in all
copies or substantial portions of the Software.
</p>
<p>
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO
EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE
SOFTWARE.
</p>
</li>
<li>
<p><b>This software includes HSV-Alpha Color Picker for
Android version 3.0.1,
which is available at
<a
href="https://github.com/martin-stone/hsv-alpha-color-picker-android">
https://github.com/martin-stone/hsv-alpha-color-picker-android</a
>,
<p>Copyright (C) 2015 Martin Stone</p>
<p>
Licensed under the Apache License, Version 2.0 (the
"License");
you may not use this file except in compliance with
the License.
You may obtain a copy of the License at
</p>
<p>http://www.apache.org/licenses/LICENSE-2.0</p>
<p>
Unless required by applicable law or agreed to in
writing, software
distributed under the License is distributed on an "AS
IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
express or implied.
See the License for the specific language governing
permissions and
limitations under the License.
</p>
</li>
<li>
<p><b>This software includes AndroidUn7zip version 1.7.1,
which is available at
<a href="https://github.com/hzy3774/AndroidUn7zip">
https://github.com/hzy3774/AndroidUn7zip</a>,
<p>Copyright (C) 2019 HuZongYao</p>
<p>
Licensed under the Apache License, Version 2.0 (the
"License");
you may not use this file except in compliance with
the License.
You may obtain a copy of the License at
</p>
<p>http://www.apache.org/licenses/LICENSE-2.0</p>
<p>
Unless required by applicable law or agreed to in
writing, software
distributed under the License is distributed on an "AS
IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
express or implied.
See the License for the specific language governing
permissions and
limitations under the License.
</p>
</li>
<li>
<p><b>CircuitSafari includes SPICE models provided by Texas
Instruments. The following terms apply to your use of these SPICE
models:</b></p>
<p>(C) Copyright Texas Instruments Incorporated. All rights
reserved.</p>
<p>This model is designed as an aid for customers of Texas
Instruments. TI and its licensors and suppliers make no warranties,
either expressed or implied, with respect to this
model, including the warranties of merchantability or fitness for a
particular purpose.
The model is provided solely on an "as is" basis. The
entire risk as to its quality and performance is with the customer.
<p>This model is subject to change without notice. Texas
Instruments Incorporated is not responsible for updating this
model.</p>
</li>
<li>
<p><b>This software includes model parameter menus that are
derived from
(Vogt et al., 2021), requiring the following notice:</b></p>
<p>The database the model parameter menus are based on is
downloadable from
<a
href="https://www.logipipe.com/circuitsafari">https://www.logipipe.com/
circuitsafari</a>.</p>
</li><li>
<p><b>This software includes code for importing and exporting
some KiCad file formats
documented in (KiCad Developers Team, n.d.).</b></p>
</li></ul>
<div class="heading"><h4>References</h4></div>
<ol>
<li>
KiCad Developers Team. (n.d.). File Formats | KiCad EDA.
Retrieved Febuary 16, 2019, from <a
href="http://kicad-pcb.org/help/file-formats/">
http://kicad-pcb.org/help/file-formats/</a>
</li>
<li>
Vogt, H., Hendrix, M., Nenzi, P., & Warning, D. (2021).
<i>Ngspice User's Manual Version 35</i>.
Retrieved December 27, 2021, from <a
href="http://ngspice.sourceforge.net/docs/ngspice-35-manual.pdf">
http://ngspice.sourceforge.net/docs/ngspice-35-manual.pdf</a>
</li>
</ol>
</body>
</html>

Help CircuitSafari Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Help CircuitSafari Manual

Uploaded by

Copyright:

Available Formats

<!

<p>To make a connection, single tap on a pin or wire to select it

<p>To disconnect a wire, tap on a wire to select it. To

<p>To move components, specify the components to be moved by

<p>A rectangular region of components can be selected by hitting

<p>The menu button serves a dual purpose, depending on whether or not a

<p>Selected components can be moved to a different

<p>To rotate selected parts counterclockwise, tap the rotate

<p>Component attributes can be edited by double tapping on a

<p>A spice directive can be specified by placing a text component

<p>Components with a model name attribute have some of their

<p>To save a schematic to a new file, hit "Google Drive->Save

<p>Since CircuitSafari only has the ability to see files in

<p>CircuitSafari's built in text editor can be used to upload a

<p>If the desired file is hidden in a ZIP file, hit "Google

<p>To move files from within CircuitSafari's Google Drive file

<a class="anchor" id="simulator"></a>

<p>Once a schematic has been entered, it can be simulated by

<a class="anchor" id="subcircuits"></a>

<p>The only difference between a root circuit and

<p>The icon for a subcircuit reference looks like an 8 pin DIP IC in

<p>The symbol for a subcircuit is automatically generated from

<p>To navigate to a subcircuit specification from a referencing

<p>Formal arguments can be passed to a subcircuit by placing a .formal

<p>To be able to reference the subcircuit specification from another

<p>A subcircuit may be defined by an unencrypted PSpice compatible

<a class="anchor" id="digital_logic"></a>

<p>Digital logic elements need a power and ground connection.

<a class="anchor" id="arithmetic_expressions"></a>

<a class="anchor" id="archive_files"></a>

<p>Permission is hereby granted, without written agreement and

<p>IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY

<p>Software is distributed as is, completely without warranty or

<p>The University of California hereby disclaims all implied

<p>The University of California grants the users the right to

<li>In any product based on the software, the users agree to

<li>The users agree to obey all U.S. Government restrictions

<li>The users agree to reproduce any copyright notice which

<p>Chenming Hu, and Weidong Liu<br />

<p>Hiroshima University and STARC own the copyright and

<p>Hiroshima University and STARC hereby disclaim all

<p>Hiroshima University and STARC grant the users the right

<li>The users agree to reproduce any copyright

<li>As the owner of the HiSIM_HV intellectual property, and

<li>A Licensee of HiSIM_HV intellectual property agrees that

<p>"The HiSIM_HV source code, and all copyrights, trade

<li>A Licensee of HiSIM_HV intellectual property will comply

<li>By using HiSIM_HV intellectual property owned by

<li>Downloading the STAG Model deems acceptance of the terms

<li>DERA grants to LICENSEE a royalty free non-exclusive

<li>LICENSEE acknowledges that STAG is a research tool still

<li>LICENSEE acknowledges that STAG is a Model developed by

<li>LICENSEE undertakes to obtain any separate licence

<li>DERA make no representations or warranties, express or

<li>Title to copyright of all portions of STAG developed at

<li>This agreement shall be construed, interpreted, and

<p>for DERA by:</p>

<p>Intellectual Property Department<br />

<p>phone: � - 1684 - 894234<br />

<p>Copyright (c) 2011-2014, The OpenBLAS Project<br />

<p>Redistribution and use in source and binary forms, with or

<li>Redistributions in binary form must reproduce the above

<li>Neither the name of the OpenBLAS project nor the names of