JLAB is a set of Matlab functions I have written or co-written over the past fifteen years for the purpose of analyzing data. It consists of four hundred m-files spanning thirty thousand lines of code. JLAB includes functions ranging in complexity from one-line aliases to high-level algorithms for certain specialized tasks. These have been collected together and made publicly available for you to use, modify, and --- subject to certain very reasonable constraints --- to redistribute.
Some of the highlights are: a suite of functions for the rapid manipulation of multi-component, potentially multi-dimensional datasets a systematic way of dealing with datasets having components of non-uniform length tools for fine-tuning figures using compact, straightforward statements and specialized functions for spectral and time / frequency analysis, including advanced wavelet algorithms developed by myself and collaborators.
This version of the book is a DRAFT! The chapters are mostly complete, but not carefully edited. Some of the debugging sections are not done, and not all chapters have exercises.
If you have high-level comments about the organization of the book or the topics covered, please send me email at feedback{at}thinkpython{dot}com. It is probably too early for detailed comments like spelling errors.
This sample provides a generic example of a PCI IDE minidriver. The sample isolates vendor-specific code from the higher-level PCI IDE bus driver, much as SCSI minidrivers isolate code from the SCSI port driver. See the Release Notes section for more information.
This sample works on both x86 and Alpha platforms, and is 64-bit compliant. It builds with Microsoft® Visual C® 6.0. It does not implement Plug and Play or Power Management.
This code is described in "Computational Geometry in C" (Second Edition),
Chapter 8. It is not written to be comprehensible without the
explanation in that book.
Prints out one arm configuration to reach given target.
Assumes number of links >= 3.
Input:
nlinks Number of links
L1 L2 ... Ln Link lengths
x0 y0 target0
x1 x2 target1
看n2實例 #Create a simulator object
set ns [new Simulator]
#Define different colors for data flows
#$ns color 1 Blue
#$ns color 2 Red
#Open the nam trace file
set nf [open out-1.nam w]
$ns namtrace-all $nf
set f0 [open out0.tr w]
set f1 [open out1.tr w]
#Define a finish procedure
proc finish {} {
global ns nf
$ns flush-trace
#Close the trace file
close $nf
#Execute nam on the trace file
exit 0
}
#Create four nodes
set n0 [$ns node]
set n1 [$ns node]
set n2 [$ns node]
set n3 [$ns node]
#Create links between the nodes
$ns duplex-link $n0 $n2 1Mb 10ms
AppWizard has created this ac1080 application for you.
This file contains a summary of what you will find in each of the files that
make up your ac1080 application.
ac1080.dsp
This file (the project file) contains information at the project level and
is used to build a single project or subproject. Other users can share the
project (.dsp) file, but they should export the makefiles locally.
ac1080.cpp
This is the main application source file.
This file contains a summary of what you will find in each of the files that
make up your ac_iocard application.
ac_iocard.dsp
This file (the project file) contains information at the project level and
is used to build a single project or subproject. Other users can share the
project (.dsp) file, but they should export the makefiles locally.
ac_iocard.cpp
This is the main application source file.
RCPServer.cpp
This the main application source file.
RCPServer.dsp
This file (the project file) contains information at the project level and
is used to build a single project or subproject. Other users can share the
project (.dsp) file, but they should export the makefiles locally.
