Portfolio Website Project:
Made with CSS flexbox grid layout
github
Giftshopstop Project: www
This was a freelance project. My client wanted to sell her handmade quilts online. It was made with Materialize;
A modern, responsive front-end framework based on Material Design.
It included full encryption on both the front
and back end for money transfers.
I turned the button's off due to business closure.
Code Sample:
This is a sample of one of the forty-two cards I used to display the products. The customer can purchase
using
credit, debit, or PayPal. Each purchase sends an email receipt to the customer,
and shipping directions to the
vendor. Each image includes a click magnifier.
This HTML code is for the first card titled "Diamond Squares".
Business Development Project: www
This was a class project. It was my final assignment for Business Web Development. This class focused on
front end development, and introduction to back
end development language's.
Code Sample:
This JS code is one section of the JavaScript file that animates the rotating image banner on the JS navbar link.
JS is the programming language for the web. It is used on the front-end, and on the backend. It makes projects
dynamic.
This allows them to be generated in real time, and to be interactive.
Holy Mercy Project: www
This was an independent project; my personal website to share my creative writing.
To increase Google rankings, I learned SEO techniques, and to track visitors, I learned Anyalitics.
For web forms to work successfully; HTML, CSS, JS, and PHP files work simultaneously.
Code Sample:
This PHP code is one part of many for the web form submissions on the Contact Us form.
PHP is a server side
language that runs on the server. When the user clicks the submit button, the
contactform.php is
called
using the action attribute. Then the values are submitted via HTTP PHP super global array variable
$_POST.
Web Dev & IT Project: www
This was an independent project. I did it to become more familiar with flexbox grid layout features.
Flexbox and grid are CSS layout modules that allows creation of complex layouts.
They share
multiple similarities, though are different, and many layouts can be solved using both.
Code Sample:
This CSS code defines the size of the .top-container class. The .showcase class defines
the
grid-template-areas: I am using CSS variables defined by a scope of root as shown in
box-shadow: var(--shadow); This code is for the three boxes directly below the navbar titled
"Welcome to Web-Dev & IT", "Branding & Renovating", and "Information Technology".


{% extends "generic.html" %} {% block header %} {{ entry.title }} {% endblock %} {% load static %} {% if error_message %}
{{ error_message }}
{% endif %} {% block content %}This entry describes setting up a npm server integrating a webassembly library written in Rust as explained in Conway's Game of Life. This demo uses a Javascript front-end, makes a call to webassembly, passes a variable in, and retrieves a variable synchronously.
Pull down a Rust template and follow instructions to name project.
cargo generate --git https://github.com/rustwasm/wasm-pack-template
tree wasm-game-of-life
wasm-game-of-life/
├── Cargo.toml
├── LICENSE_APACHE
├── LICENSE_MIT
├── README.md
└── src
├── lib.rs
└── utils.rs
cd wasm-game-of-life
Slighty modify the src/lib.rs file.
#[wasm_bindgen]
pub fn greet(s: String) -> String {
let st = format!("Hello {}, test wasm-game-of-life!", s);
alert(&st);
format!("Yay, I work")
}
Build the rust library.
wasm-pack build
Create npm project.
npm init wasm-app www
cd www
Slighty modify index.js
var s = wasm.greet("John");
document.body.textContent = s;
Slightly modify package.json
"dependencies": {
"wasm-game-of-life": "file:../pkg"
}
Install libraries and start server
npm install
npm run start
{% endblock %}


OTET Results 2019: Results for Odisha Teacher Eligibility Test 2019 released @ bseodisha.ac.in
by JKR StaffOTET Results 2019: The results for Odisha Teacher Eligibility Test 2019 has been released on the official website of the Board of Secondary Education, Odisha, bseodisha.ac.in and bseodisha.nic.in.
The pass percentage or criteria for the state-level teacher eligibility test was a minimum of 60% marks in the eligibility exam in order to be able to teach students from from classes 1 to 8.
Follow these steps to access your results
- Visit official exam portal of BSE Odisha bseodisha.ac.in
- Locate and click Examinations Tab in the top menu
- Select OTET Exam from the drop-down menu
- You will be redirected to the dedicated portal for OTET Exam
- Locate and Click the OTET 2019 Result Link on the page
- Input the details asked on the page
- Your OTET Result 2019 will be displayed on the screen
- Download the Scorecard and take a printout for future reference
About BSE Odisha
The Board of Secondary Education, Odisha is a Body Corporate constituted under the Odisha Secondary Education Act, 1953. It regulates, controls and develops Secondary Education in the State of Odisha. It Provides varied courses in order to equip students for different occupations, to prepare them for University education and to equip them for various cultural purposes. It examines those who have completed a prescribed course of study and awards certificates to the successful candidates. Besides, it does all other things which are incidental to the above.
functions of the Board are :
- To conduct High School Certificate Examinations (H.S.C.E.) and examinations of other courses prescribed by the Board.
- To prepare courses of studies, text books, teaching materials etc.
- To publish and distribute/sell text books, syllabuses, lesson notes, work books and other related materials.
- To issue certificates of the examinations conducted by the Board and equivalence certificate to the examinations of other State Boards.
- To recognise the secondary schools for the examinations of the Board.
- To make regulations for undertaking different functions of the Board.
- To take care of Secondary Education through Orientation Programmes, Refresher Courses and other academic programmes.


ISBN Search
ISBN-13:<PHONE_NUMBER>906
ISBN-10:<PHONE_NUMBER>
Authors: Michael Sikorski; Andrew Honig
Edition: 1
Binding: Paperback
Publisher: No Starch Press
Published: February 2012
List Price: $59.95
$34.77
Free shipping
Ready to ship
Notes
$32.22
+3.95 shipping
$36.29
+3.99 shipping
$35.84
Ships 3+ Days
$36.42
+3.50 shipping
Ships 2-3 days
$36.26
$43.22
$42.96
+4.96 shipping
$46.80
+3.97 shipping
$24.92
+3.00 shipping
$25.61
$28.17
$28.03
$18.99
+5.99 shipping
$44.51
$44.96


Sir Ed Davey pledges £100bn to tackle the climate crisis
by Edward ThicknesseLiberal Democrat deputy leader Ed Davey this afternoon laid out his party’s economic plans, announcing that his party would spend an additional £100bn of public finance on tackling the climate crisis.
Speaking at an event in Leeds, the party’s shadow chancellor said: “This includes a new £10bn renewable power fund to leverage in over £100bn of extra private climate investment.
Read more: Boris Johnson unveils Brexit-branded election battle bus
“This will fast-track deployment of clean energy, to make Britain not just the world leader in offshore wind, but also the global number one in tidal power too.
“And we will invest £15bn more to make every building in the country greener, with an emergency ten-year programme to save energy, end fuel poverty and cut heating bills.”
Davey pointed to his own track record in delivering renewable energy projects, saying that as secretary of state for energy and climate change under the coalition government he had led “stage one of Britain’s decarbonisation”:
“I’ve seen what we did in government. And I know what we can do in government again.”
Davey also hit out at the Conservatives, saying that the government had “made our economy weak”, and criticising the “fantasy economics” of both the Tory and Labour election pledges:
“So far, the economy debate in this election has been a debate between fantasies. Fantasies born of nostalgia for a British Imperial past, competing with fantasies from a failed 1970s ideology.”
In addition, Davey said that the extra growth that the UK would enjoy as a result of his party’s principal pledge to stop Brexit would generate “a £50bn Remain bonus” for the country.
He pledged that the Liberal Democrats would use the money to invest in the UK’s human capital, its schools, and its infrastructure.
Read more: BT CEO warns Labour’s part nationalisation of BT could cost £100bn
In a dig at Labour’s marquee British broadband announcement this morning, he also promised that his party would not “put Big Brother in charge of your digital broadband.
“Lib Dems won’t waste your taxes and scare of private investment
with a nonsense return back to state-owned telecoms – where long delays and
low quality were the order of the day.”
Main image credit: Getty


- indexOf(String) - Method in class io.delta.kernel.types.StructType
-
- INSTANCE - Static variable in class io.delta.kernel.types.BooleanType
-
- INSTANCE - Static variable in class io.delta.kernel.types.IntegerType
-
- INSTANCE - Static variable in class io.delta.kernel.types.LongType
-
- INSTANCE - Static variable in class io.delta.kernel.types.StringType
-
- INSTANCE - Static variable in class io.delta.kernel.types.UnresolvedDataType
-
- IntegerType - Class in io.delta.kernel.types
-
- InvalidExpressionException - Exception in io.delta.kernel
-
- InvalidExpressionException() - Constructor for exception io.delta.kernel.InvalidExpressionException
-
- io.delta.kernel - package io.delta.kernel
-
Delta Kernel interfaces for constructing table object representing a Delta Lake table, getting
snapshot from the table and building a scan object to scan a subset of the data in the table.
- io.delta.kernel.client - package io.delta.kernel.client
-
Interfaces to allow the connector to bring their own implementation of functions such
as reading a parquet files, listing files a file system, parsing a JSON string etc.
- io.delta.kernel.data - package io.delta.kernel.data
-
Delta Kernel interfaces for representing data in columnar and row format.
- io.delta.kernel.expressions - package io.delta.kernel.expressions
-
Expressions framework that defines the most common expressions which the connectors
can use to pass predicates to Delta Kernel.
- io.delta.kernel.fs - package io.delta.kernel.fs
-
Utilities to represent files.
- io.delta.kernel.types - package io.delta.kernel.types
-
Data types defined by the Delta Kernel to exchange the type info between the Delta Kernl and
the connectors.
- io.delta.kernel.utils - package io.delta.kernel.utils
-
Utilities.
- isAbsolute() - Method in class io.delta.kernel.fs.Path
-
Returns true if the path component (i.e.
- isAbsoluteAndSchemeAuthorityNull() - Method in class io.delta.kernel.fs.Path
-
Returns true if the path component (i.e.
- isHasDeletionVector() - Method in class io.delta.kernel.fs.FileStatus
-
Whether this file has any associated deletion vector?
- isNullable() - Method in class io.delta.kernel.types.StructField
-
- isNullAt(int) - Method in interface io.delta.kernel.data.ColumnVector
-
Returns whether the value at rowId
is NULL.
- isNullAt(int) - Method in interface io.delta.kernel.data.Row
-
Is the column at given ordinal has null value?
- isRoot() - Method in class io.delta.kernel.fs.Path
-
Returns true if and only if this path represents the root of a file system.
- isUriPathAbsolute() - Method in class io.delta.kernel.fs.Path
-
Returns true if the path component (i.e.
- isValueContainsNull() - Method in class io.delta.kernel.types.MapType
-
- isWindowsAbsolutePath(String, boolean) - Static method in class io.delta.kernel.fs.Path
-
Determine whether a given path string represents an absolute path on
Windows.


Hello there, awesome person!
My Awesome Web Page
This is the largest heading in my page
This is the second largest heading in my page
This is the third largest heading in my page
This is the fourth largest heading in my page
This is the fifth largest heading in my page
This is the smallest heading in my page
This is the link to the course teach yourself Computer Science
freebootcamp.com
My favourite website is
programiz.com
thejsbootcamp.com
shayhowe.com
This is where the text goes


the x-coordinate of the voxel (in meter units)
the y-coordinate of the voxel (in meter units)
the z-coordinate of the voxel (in meter units)
the scale of the voxel (in meter units)
If the scripting context has visible voxels, this will determine a ray intersection, the results may be inaccurate if the engine is unable to access the visible voxels, in which case result.accurate will be false.
If the scripting context has visible voxels, this will determine a ray intersection, and will block in order to return an accurate result
returns a voxel space axis aligned vector for the face, useful in doing voxel math
provide the world scale.
checks the local voxel tree for a voxel at the specified location and scale
the x-coordinate of the voxel (in meter units)
the y-coordinate of the voxel (in meter units)
the z-coordinate of the voxel (in meter units)
the scale of the voxel (in meter units)
checks the local voxel tree for the smallest voxel enclosing the point
the x,y,z coordinates of the point (in meter units)
VoxelDetail - if no voxel encloses the point then VoxelDetail items will be 0
checks the local voxel tree for the smallest voxel enclosing the point and uses a blocking lock
the x,y,z coordinates of the point (in meter units)
VoxelDetail - if no voxel encloses the point then VoxelDetail items will be 0
queues the destructive creation of a voxel which will be sent by calling process on the PacketSender
the x-coordinate of the voxel (in meter units)
the y-coordinate of the voxel (in meter units)
the z-coordinate of the voxel (in meter units)
the scale of the voxel (in meter units)
the R value for RGB color of voxel
the G value for RGB color of voxel
the B value for RGB color of voxel
queues the creation of a voxel which will be sent by calling process on the PacketSender
the x-coordinate of the voxel (in meter units)
the y-coordinate of the voxel (in meter units)
the z-coordinate of the voxel (in meter units)
the scale of the voxel (in meter units)
the R value for RGB color of voxel
the G value for RGB color of voxel
the B value for RGB color of voxel
Generated using TypeDoc
queues the deletion of a voxel, sent by calling process on the PacketSender


Bullet Collision Detection & Physics Library
src
BulletCollision
NarrowPhaseCollision
Classes
btGjkEpa2.h File Reference
#include "
BulletCollision/CollisionShapes/btConvexShape.h
"
Include dependency graph for btGjkEpa2.h:
This graph shows which files directly or indirectly include this file:
Go to the source code of this file.
Classes
struct
btGjkEpaSolver2
btGjkEpaSolver contributed under zlib by Nathanael Presson
More...
struct
btGjkEpaSolver2::sResults
Generated by
1.8.13


Curve velocity
is in
the outward direction
with
speed decaying with image edge strength
xt
=
R xs / ||xs||
× f(||D(Gσ∗I)(x)||)
Example 1 (initialization failure)
Curve velocity
is in
the outward direction
with
speed decaying with image edge strength
xt
=
R xs / ||xs||
× f(||D(Gσ∗I)(x)||)
Example 1 (velocity repairs)
Curve velocity
is in
the outward direction
with
speed decaying with image edge strength
and
contracts in bright areas
xt
=
R xs / ||xs||
× f(||D(Gσ∗I)(x)||)
× sign(T-I(x))
Example 2
Curve velocity
is in
the outward direction
with
speed decaying with image edge strength
and
contracts in bright areas
xt
=
R xs / ||xs||
× f(||D(Gσ∗I)(x)||)
× sign(T-I(x))
Implicit curve evolution: level set framework
Implicit curve = {x : u(x,t) = 0}
Enforce level curve moves in normal direction with speed V(x) yields level set evolution PDE: ut + V ||Du|| = 0
Example 2
Velocity in normal directiondecays with image edge strength
and
contracts in bright areas
V(x)
= f(||D(Gσ∗I)(x)||)
× sign(T-I(x))
Some things to read
Kass, Michael, Andrew Witkin, and Demetri Terzopoulos. "Snakes: Active contour models." International journal of computer vision (1988)
Malladi, Ravi, James A. Sethian, and Baba C. Vemuri. "Shape modeling with front propagation: A level set approach." IEEE transactions on pattern analysis and machine intelligence (1995)
Adalsteinsson, David, and James A. Sethian. "A fast level set method for propagating interfaces." Journal of computational physics (1995)


heading 1
this is a paragraph
this is anothr paragraph
First Name
Last Name
Xuebin
Wei
heading
2
JMU Website
Water
Soda
Coke
Sprite
Juice


The T5 CAN Flasher II is an Open Source tool used to read and write software in Trionic 5 based ECU’s.
It has a clean informative User Interface that shows rich information about your ECU and BIN file.
Easy selection of CAN adapter:
- Lawicel
- Combi
- Mictronics
- Just4Trionic
- Kvaser
Remembers your selection for next time.
Rigorous checking of all CAN bus transfers and FLASH update progress to give you greater confidence that your FLASH actually updated.
- If it didn’t you are told about the failure and have the option to try to recover your ECU by retrying your update.
- Don’t close T5 CAN Flasher or disconnect power to your ECU otherwise you won’t be able to try to recover your ECU and BDM recovery will be your only option.
Uses a new version of MyBooty which works with more types of replacement FLASH chips:
- Atmel AT29C010A
- AT29C512 (T5.2)
- AMIC 29010L
- ST M29F010
- Microchip SST39SF010A
- AMD 29F010 chips
- Original AMD/Intel/CSI 28F010 (28F512 in T5.2 ECUs).
Can ‘convert’ a T5.5 ECU for use as a T5.2 ECU (and back again)
Update a T5.5 ECU with T5.5 a ‘standard’ 128 kB T5.2 BIN file without having to create a double T5.2 BIN first.
Reading (DUMPing) a ‘converted’ T5.5 ECU produces a standard 128 kB T5.2 BIN
Download (951 KiB)
md5: -
Changelog


Choose image to predict (PNG, JPG)
No files currently selected for predict
Predict
Predict result...


dyconnmap.chronnectomics package¶
Submodules¶
dyconnmap.chronnectomics.dwell_time module¶
Dwell Time
Dwell time measures the time (when used in the context of functional connectivity microstates) a which a state is active consecutive temporal segments (Dimitriadis2019_).
- Dimitriadis2019
Dimitriadis, S. I., López, M. E., Maestu, F., & Pereda, E. (2019). Modeling the Switching behavior of Functional Connectivity Microstates (FCμstates) as a Novel Biomarker for Mild Cognitive Impairment. Frontiers in Neuroscience, 13.
-
dyconnmap.chronnectomics.dwell_time.
dwell_time
(x)[source]¶ Dwell Time
Compute the dwell time for the given symbolic, 1d time series.
- Parameters
x (array-like, shape(N)) – Input symbolic time series.
- Returns
dwell (dictionary) – KVP, where K=symbol id and V=array of dwell time.
mean (dictionary) – KVP, where K=symbol id and V=mean dwell time.
std (dictionary) – KVP, where K=symbol id and V=std dwell time.
dyconnmap.chronnectomics.flexibility_index module¶
Flexibility Index
In the context of graph clustering it was defined in (Basset2011), flexbility is the frequency of a nodea change module allegiance; the transition of brain states between consecutive temporal segments. The higher the number of changes, the larger the FI will be.
- Basset2011
Bassett, D. S., Wymbs, N. F., Porter, M. A., Mucha, P. J., Carlson, J. M., & Grafton, S. T. (2011). Dynamic reconfiguration of human brain networks during learning. Proceedings of the National Academy of Sciences, 108(18), 7641-7646.
dyconnmap.chronnectomics.occupancy_time module¶
Occupancy Time
The fraction of number of distinct symbols occuring in the symbolic time series (Dimitriadis2019_).
- Dimitriadis2019
Dimitriadis, S. I., López, M. E., Maestu, F., & Pereda, E. (2019). Modeling the Switching behavior of Functional Connectivity Microstates (FCμstates) as a Novel Biomarker for Mild Cognitive Impairment. Frontiers in Neuroscience, 13.
Module contents¶
-
dyconnmap.chronnectomics.
dwell_time
(x)[source]¶ Dwell Time
Compute the dwell time for the given symbolic, 1d time series.
- Parameters
x (array-like, shape(N)) – Input symbolic time series.
- Returns
dwell (dictionary) – KVP, where K=symbol id and V=array of dwell time.
mean (dictionary) – KVP, where K=symbol id and V=mean dwell time.
std (dictionary) – KVP, where K=symbol id and V=std dwell time.


The B-grid dynamical core can be run as a shallow water model by
setting the number of model levels to ONE. Since the same computer
code is used for the shallow water version, some prognostic variables
represent different fields. The surface pressure (ps) now represents
the free surface geopotential height and temperature becomes another
tracer. The zonal and meridional wind components (u,v) are the same.
Not all terms can be applied in the shallow water version.
Namelist values should be set to turn off these terms.
Here is a list of terms that should not be used:
* vertical advection (set to NONE)
* slope correction in bgrid_horiz_diff (set to zero)
* energy conservation (set to FALSE)
* pgf scheme should be set to default
* sponge should probably not be used
Diagnostic fields have not been modified for the shallow water version.
Some fields have no meaning in the one level model.
(For example: zsurf, omega, pres_full, pres_half.)
PUBLIC INTERFACE
use atmosphere_mod [,only: atmosphere_init, atmosphere_end,
atmosphere,
atmosphere_resolution, atmosphere_boundary,
get_atmosphere_axes ]
NOTES
1) Optional namelist interface &atmosphere_nml may be
read from file input.nml.
PUBLIC ROUTINES
call atmosphere_init ( Time_init, Time, Time_step )
DESCRIPTION
Initialization routine for running the bgrid dynamical core.
INPUT
Time_init The base (or initial) time for the experiment.
The base time is usually subtracted from the current time
when outputting time in diagnostic routines.
[time_type]
Time The current time. [time_type]
Time_step The atmospheric model/physics time step. [time_type]
call atmosphere_end
DESCRIPTION
This routine terminates the module.
There are no arguments to this routine.
call atmosphere ( Time )
DESCRIPTION
Advances the B-grid prognostic variables one time step forward.
The dynamical core, forcing for shallow water model, diagnostics,
and time differencing are all called. This routine should only
be called once per time step.
INPUT
Time The current time. [time_type]
NOTE
The prognostic variables are stored in a private data structure
(i.e., derived-type variable) defined in the specification section
of this module.
---------------------------------------------------------------------
call get_atmosphere_axes ( axes )
OUTPUT
axes Axis identifiers for the atmospheric grids as returned by the
diagnostics manager. The size of axes must be: 1 <= size(axes) <= 4.
The axes returned are ordered: (/ x, y, p_full, p_half /).
[integer, dimension(:)]
call atmosphere_resolution ( nlon, nlat [, global] )
DESCRIPTION
Returns the resolution of compute domain for either the
current processor or the global domain.
OUTPUT
nlon The number of longitude points in the compute domain.
[integer]
nlat The number of latitude points in the compute domain.
[integer]
OPTIONAL INPUT
global Flag that specifies whether the returned compute domain size is
for the global grid (TRUE) or for the current processor (FALSE).
[logical, default: FALSE]
call atmosphere_boundary ( blon, blat [, global] )
DESCRIPTION
Returns the grid box edges of compute domain for either the
current processor or the global domain.
OUTPUT
blon The west-to-east longitude edges of grid boxes (in radians).
[real, dimension(nlon+1)]
blat The south-to-north latitude edges of grid boxes (in radians).
[real, dimension(nlat+1)]
OPTIONAL INPUT
global Flag that specifies whether the returned grid box edges are
for the global grid (TRUE) or for the current processor (FALSE).
[logical, default: FALSE]
NOTE
The size of the output arguments, blon and blat, must be +1 more than the
output arguments for call atmosphere_resolution, nlon+1 and nlat+1, respectively.


Before Change
warning = ""
// Convert to utf-8 whenever we have a binary input.
if isinstance(markdown_string, six.binary_type):
markdown_string_decoded = markdown_string.decode("utf-8")
// Remove null bytes and warn if there were any, since it probably means
// we were given a bad encoding.
markdown_string = markdown_string_decoded.replace(u"\x00", u"")
num_null_bytes = len(markdown_string_decoded) - len(markdown_string)
if num_null_bytes:
warning = (
"<!-- WARNING: discarded %d null bytes in markdown string "
"after UTF-8 decoding -->\n"
) % num_null_bytes
string_html = _MARKDOWN_STORE.markdown.convert(markdown_string)
string_sanitized = bleach.clean(
string_html, tags=_ALLOWED_TAGS, attributes=_ALLOWED_ATTRIBUTES
)
After Change
Returns:
A string containing safe HTML.
return markdowns_to_safe_html([markdown_string], lambda xs: xs[0])
def markdowns_to_safe_html(markdown_strings, combine):


Ruby: Blocks, Procs, & LambdasNov 14th
Photo credit: therefromhere / Foter / CC BY-NC-SA
Blocks
What is a block, proc, and lambda, and how are they used? We've actually already seen blocks. Can you spot them here?
["A","B","C"].each do |letter| puts letter end ["A","B","C"].each { |letter| puts letter}
Here are two blocks being called for the each method.
do |letter| puts letter end { |letter| puts letter}
Procs
Blocks are useful to allow methods to do more complex operations. However, they cannot be taken out of context and do not allow for more than block to be passed into a method argument. What if we want to reuse the logic written in the block and apply it to other objects? This is where Procs come in.
printer = Proc.new {|letter| puts letter}
Procs are actually objects themselves!
printer.class => Proc
How can we use a proc? Well, since the method each can only take in a single block, we can send it a proc while using a special operator, '&' in order to tell Ruby to treat this as a block. Let's call the each method on our letters array and see what we get.
letters = ["A","B","C"] printer = Proc.new {|letter| puts letter} letters.each(&printer) A B C
Procs will certainly help us keeping our code DRY. Let's see an example of one way to reuse procs.
def sequence_procs(proc1, proc2, proc3) proc1.call proc2.call proc3.call end first = Proc.new { puts "Running first proc..." } second = Proc.new { puts "Running second proc..." } third = Proc.new { puts "Running third proc..." }
Here, we have set up a method that will take in three proc arguments and will call them in a sequence. What do you think will output?
sequence_procs(first, second, third)
Running first proc... Running second proc... Running third proc...
Lambdas
We can think of Lambdas as the same thing as procs with a few subtle differences. Here's how a lambda is created. This should look very familiar.
letters = ["A","B","C"] lamb_printer = lambda {|letter| puts letter} letters.each(&lamb_printer)
A B C
A key distinction should be made when we ask a proc or lambda to return something. Let's first look at how a Proc would return a string within a method. Pay attention to the result object.
def try_proc result = Proc.new { return "Here is the proc." } result.call p "End of proc method." end p try_proc
=> "Here is the proc."
Our proc is being called on this object, so normally we would expect the string "Here is the proc." to be returned to result object, and not when calling the method. Normally we expect try_proc to display "End of proc method", but this is not the case. Proc does not care about the context in this case, and acts as if the method itself is returning "Here is the proc". Let's see what happens when we use a lambda.
def try_lambda result = lambda { return "Here is the lambda" } result.call p "End of lambda method." end p try_lambda
"End of lambda method."
Here, nothing is returned from the method itself. Instead, the code runs through and prints the "End of the lambda method". This is more conventional since it behaves exactly as we'd expect according to principles of scope. Procs being context insensitive can be beneficial as long as they are used with discretion.


GETTING AROUND THE MAP: Navigation
There are a number of ways to navigate around the map using the zoom in/out buttons on the map, the "Find my location" button, and your mouse and keyboard.
- The "Zoom In/Out" buttons will incrementally zoom the map in/out. Zoom in using your mouse scroll wheel by placing the cursor over the center of the area you would like to zoom in to and scroll the mouse wheel (**) up. Scroll the mouse wheel down to zoom out. Also, if you double-click (or double-tap on touch-capable devices) somewhere on the map, it will incrementally zoom in to where you double-clicked. Those with touch-enabled devices can also zoom in/out by pinching/expanding two fingers on the screen.
**
You can pan (move around) the map by holding the left-mouse button (or your finger on touch-enabled devices) down and moving the cursor around or use the up, down, left, and right arrow keys on the keyboard.
- The "Find My Location" button will locate, zoom to, and add a purple icon at your current location. To disable this feature, refresh your page (press the F5 button).
You may also find the coordinate indicator text (located in the bottom right corner of the map) useful for navigating to a location. To navigate to a specific latitude, longitude coordinate use the Place or Coordinate Search tool.
The scale bar will give you some idea about the size of an area but to gather more information about distance and area use the Measurements & Coordinates tool.
Created with the Personal Edition of HelpNDoc: Free CHM Help documentation generator


--- layout: default title: Composing Compound Predicates ---
Here are two sentences:
Egypt began as a group of villages. It became one of the first great civilizations.
There are two predicates.
The predicates are underlined.
Both of the predicates tell about Egypt.
We can join the two predicates with "and" like this:
Egypt began as a group of villages and became one of the first great civilizations.
Here is another example. See if you can find the predicates.
The pharaoh was the most important person. He made all the big decisions.
Here is how we use "and" to join the predicates:
The pharaoh was the most important person and made all the big decisions.


Gliptal wrote:
Would it be possible to implement a method (through a button or similar) to apply a given camo to all unlocked weapons and to all vehicles? As it is now, keeping camos consistent through all the equipment is an extremely daunting task.
Also, will it ever be possible to see (and maybe even change) soldier camos in the Battlelog? Right now it can only be done ingame.
As a random note on this, applying paint across all weapons and, independent from that, all vehicles is now thankfully integrated in vanilla battlelog/bf4.
Soldier camos are a much more complicated issue. They're actually find-able in the underlying data of the page, but I haven't had a great deal of luck finding an efficient means of a) IDing which is which and b) getting changes to it to reliably stick game-side, especially since the soldier camos are per-faction, so jumping between US, CN, and RU really just makes a complicated mess of it.


Contents
Sprint Plan
Here are the user stories/tasks we plan to finish for this sprint:
Tasks labelled with red signifies the tasks we plan to finish.
Here's our sprint plan/story point assignment:
Burndown Chart
User Stories/Personas
We did not update our user stories for this sprint since we finished all the leftover tasks from the last sprint. User stories can be seen here.
Sprint Report
Most of this sprint was dedicated towards completing leftover tasks from sprint 3 and testing our application. We started out the sprint by fixing bugs introduced by automatically generated Android code. We then moved on to completing the student submission backend, which was notable because we needed to go back and refactor some broken database code which took time out of completing our other tasks. At the same time the UI layout for creating assignments and answering assignments was being developed, which was hooked up to the backend after solving a few bugs.
For this sprint we continued to split the developer roles between backend/frontend. We added some tasks to address testing requirements, which was coded using JUnit. We greatly underestimated how long it takes to thoroughly test, since testing 1 class took about 5 hours.
Taskboard Snapshots
Before sprint execution:
After sprint execution:
Tasks labelled with green are done.
Tasks labelled with yellow are in progress.
Tasks labelled with red are not done.
Verification
For unit testing, we used the JUnit 4 testing framework. To run our tests, open the Stapp folder with Android Studio. After it is done loading, open the "app->java->com.stapp (androidTest)" folder. Then, right click on the "com.stapp (androidTest)" folder in the project explorer, and click the "Run tests in com.stapp" option.
Then, choose a target device. You will need to connect an Android phone or use a virtual Android phone to run the tests. After choosing a device, all the unit tests should run. You can see the results of the unit tests at the bottom of the Android Studio window.
Validation
For each UI-related task we completed for this sprint, we validated each one by writing reproducible steps with the expected result.
T23: After opening a course from a list of courses, need to be able to view a list of assignments
- Login as a professor (you can use username: nick, password: nick)
- Add a new course using the Add Course button
- Input the course code "CSCA08" and press done
- Back at the professor home page, you will see CSCA08 as a course
Code Review Strategy
- Each person should read another person's code (not your own code!)
- Note what we should stop doing and start doing.
- After each method, write down what you think could be improved.
- After each class, try to summarize your notes into 1-3 points that can be expanded on during the meeting.
- Don't single out people or be insensitive about your code being criticized. It should be a learning experience.
- Don't take a code review personally. It's just code!
- Use the Github commit log to easily see other people's code at a glance.
Code Review Summary
J.R.'s points:
- Code style needs to be consistent. In some files, 2-space tabs are used instead of 4-space tabs.
- We need to keep our code lines short. Especially in the DatabaseDriver class, lines should be kept under 80 characters long.
- This can be solved with linting software, to automatically employ Google style guide.
Harry(HaoYue)'s points:
- Basic fundamentals of Object Oriented Programming were used correctly: Polymorphism, Inheritance, Interface, Encapsulation/Visibility, etc.
- Front-end and back-end codes are separated, in a way that's not confusing.
- Related functions and methods are grouped in the same package, making it very easy to navigate.
- Overall good organization and well structured packages, every package has its purpose and it is separated in a way that's easily distinguishable in terms of functions.
- File and package naming convention inconsistencies.
- XML file organization, activity vs. content XML files.
Rahul's points:
- Maintain good coding practices!
- Make sure to use javadocs for methods that have a complicated algorithm.
- Naming should follow camelCase for consistent style.
- Classes do work as intended but you should try to keep formatting consistent with the other classes.
- Inline comments would be useful for some important lines to make sure we understand what you've written.
Wen Bo's Points:
- We should adopt the Strategy Design Pattern
- The helper function can be fused with the regular class
- make use of interface so we can do mock testing
- certain method is impossible to test because we didn't implement Strategy Design Pattern
- Should make a release that can be shown to the client i.e Sohee Kang sooner
Richard's Points
- All static strings should be coded in res/strings.xml for good coding practice
- Any instances of floating action buttons should be removed as they are unused and auto-generated
- The Recyclers should display thier contents more clearly, and as more obviously click-able
- Layout student_menu_activity.xml needs to be restructured to align the Recycler properly
- The Assignment creation should use a DatePicker widget for selecting due dates


- waitFor(File, int) - Static method in class com.knowgate.io.FileUtils
-
Waits for NFS to propagate a file creation, imposing a timeout.
- WEDNESDAY - Static variable in class com.knowgate.dateutils.GregorianCalendarLocalisation
-
- WeekDayName(int, String) - Static method in class com.knowgate.dateutils.GregorianCalendarLocalisation
-
Get translated week day name
- wildcardMatch(String, String) - Static method in class com.knowgate.io.FilenameUtils
-
Checks a filename to see if it matches the specified wildcard matcher,
always testing case-sensitive.
- wildcardMatch(String, String, IOCase) - Static method in class com.knowgate.io.FilenameUtils
-
Checks a filename to see if it matches the specified wildcard matcher
allowing control over case-sensitivity.
- wildcardMatchOnSystem(String, String) - Static method in class com.knowgate.io.FilenameUtils
-
Checks a filename to see if it matches the specified wildcard matcher
using the case rules of the system.
- write(char[]) - Static method in class com.knowgate.debug.DebugFile
-
Write trace
If setFile() has not been called, traces are written to /vagrant/tmp/ on
UNIX systems or C:\Temp\Debug on Windows
- write(String) - Static method in class com.knowgate.debug.DebugFile
-
Write trace
Traces are written to /tmp/javatrc.txt on UNIX systems or C:\TEMP\Debug\javatrc.txt on Windows
- write(byte[], OutputStream) - Static method in class com.knowgate.io.IOUtils
-
Writes bytes from a byte[]
to an OutputStream
.
- write(byte[], Writer) - Static method in class com.knowgate.io.IOUtils
-
Writes bytes from a byte[]
to chars on a Writer
using the default character encoding of the platform.
- write(byte[], Writer, String) - Static method in class com.knowgate.io.IOUtils
-
Writes bytes from a byte[]
to chars on a Writer
using the specified character encoding.
- write(char[], Writer) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a char[]
to a Writer
using the default character encoding of the platform.
- write(char[], OutputStream) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a char[]
to bytes on an
OutputStream
.
- write(char[], OutputStream, String) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a char[]
to bytes on an
OutputStream
using the specified character encoding.
- write(String, Writer) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a String
to a Writer
.
- write(String, OutputStream) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a String
to bytes on an
OutputStream
using the default character encoding of the
platform.
- write(String, OutputStream, String) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a String
to bytes on an
OutputStream
using the specified character encoding.
- write(StringBuffer, Writer) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a StringBuffer
to a Writer
.
- write(StringBuffer, OutputStream) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a StringBuffer
to bytes on an
OutputStream
using the default character encoding of the
platform.
- write(StringBuffer, OutputStream, String) - Static method in class com.knowgate.io.IOUtils
-
Writes chars from a StringBuffer
to bytes on an
OutputStream
using the specified character encoding.
- writeByteArrayToFile(File, byte[]) - Static method in class com.knowgate.io.FileUtils
-
Writes a byte array to a file creating the file if it does not exist.
- writeLines(File, String, Collection) - Static method in class com.knowgate.io.FileUtils
-
Writes the toString()
value of each item in a collection to
the specified File
line by line.
- writeLines(File, Collection<String>) - Static method in class com.knowgate.io.FileUtils
-
Writes the toString()
value of each item in a collection to
the specified File
line by line.
- writeLines(File, String, Collection<String>, String) - Static method in class com.knowgate.io.FileUtils
-
Writes the toString()
value of each item in a collection to
the specified File
line by line.
- writeLines(File, Collection<String>, String) - Static method in class com.knowgate.io.FileUtils
-
Writes the toString()
value of each item in a collection to
the specified File
line by line.
- writeLines(Collection, String, OutputStream) - Static method in class com.knowgate.io.IOUtils
-
Writes the toString()
value of each item in a collection to
an OutputStream
line by line, using the default character
encoding of the platform and the specified line ending.
- writeLines(Collection, String, OutputStream, String) - Static method in class com.knowgate.io.IOUtils
-
Writes the toString()
value of each item in a collection to
an OutputStream
line by line, using the specified character
encoding and the specified line ending.
- writeLines(Collection, String, Writer) - Static method in class com.knowgate.io.IOUtils
-
Writes the toString()
value of each item in a collection to
a Writer
line by line, using the specified line ending.
- writeln(String) - Static method in class com.knowgate.debug.DebugFile
-
Write trace and append line feed
- writeln(char[]) - Static method in class com.knowgate.debug.DebugFile
-
Write trace and append line feed
- writeStackTrace(Throwable) - Static method in class com.knowgate.debug.DebugFile
-


Disclaimer
The medical information on this site is provided as an information resource only, and is not to
be used or relied on for any diagnostic or treatment purposes. This information is not intended
to be patient education, does not create any patient-physician relationship, and should not be
used as a substitute for professional diagnosis and treatment.
Please consult your health care provider before making any healthcare decisions or for guidance
about a specific medical condition. Narayana expressly disclaims responsibility, and shall have
no liability, for any damages, loss, injury, or liability whatsoever suffered as a result of
your reliance on the information contained in this site. Narayana
does not endorse specifically any test, treatment, or procedure mentioned
on the site.
By visiting this site you agree to the foregoing terms and conditions, which may from time to
time be changed or supplemented by Narayana.


{% extends 'layout.html' %} {% block title %}Password Reset | {{ block.super }}{% endblock %} {% block content %}
Your new password has been set! You should be all set to log in.


<% if status == 'running': # begin %>
Status:
Running
Click to stop.
<% # end elif status == 'stopped': # begin %>
Status:
Stopped
Click to start.
<% # end elif status == 'suspended': # begin %>
Status:
Suspended
Please click
here
to make a payment.
<% # end elif status == 'rebuilding': # begin %>
Status:
Rebuilding... Please Wait.
<% # end %>


-
Series ID: {{chart.timeseries.cdid}}
- Unit: {{chart.timeseries.preUnit}} {{chart.timeseries.unit}}
- {{chart.timeseries.seasonalAdjustment}}
Related time series
Datasets that contain {{chart.timeseries.name}} and related time series
This content is not available in the prototype but in future will include datasets that contain this time series and other related time series


Package org.apache.qpid.protonj2.engine
Interface EngineHandlerContext
- All Known Implementing Classes:
ProtonEngineHandlerContext
public interface EngineHandlerContext
Context provided to EngineHandler events to allow further event propagation
-
Method Summary
Modifier and TypeMethodDescriptionengine()
void
Fires the engine starting event into the next handler in theEnginePipeline
chain.void
Fires the engine state changed event into the next handler in theEnginePipeline
chain.void
fireFailed
(EngineFailedException failure) Fires theEngine
failed event into the next handler in theEnginePipeline
chain.void
fireRead
(ProtonBuffer buffer) Fires a read of ProtonBuffer events into the previous handler in theEnginePipeline
for further processing.void
fireRead
(HeaderEnvelope header) Fires a read of HeaderFrame events into the previous handler in theEnginePipeline
for further processing.void
fireRead
(IncomingAMQPEnvelope envelope) Fires a read of IncomingProtocolFrame events into the previous handler in theEnginePipeline
for further processing.void
fireRead
(SASLEnvelope envelope) Fires a read of SASL events into the previous handler in theEnginePipeline
for further processing.void
fireWrite
(ProtonBuffer buffer, Runnable ioComplete) Fires a write of ProtonBuffer events into the next handler in theEnginePipeline
for further processing.void
fireWrite
(HeaderEnvelope envelope) Fires a write of HeaderFrame events into the next handler in theEnginePipeline
for further processing.void
fireWrite
(OutgoingAMQPEnvelope envelope) Fires a write ofOutgoingAMQPEnvelope
events into the next handler in theEnginePipeline
for further processing.void
fireWrite
(SASLEnvelope envelope) Fires a write ofSASLEnvelope
events into the next handler in theEnginePipeline
for further processing.handler()
name()
-
Method Details
-
handler
EngineHandler handler()- Returns:
- the
EngineHandler
that is associated with the context.
-
engine
Engine engine()- Returns:
- the
Engine
where this handler is registered.
-
name
String name()- Returns:
- the name that assigned to this
EngineHandler
when added to theEnginePipeline
.
-
fireEngineStarting
void fireEngineStarting()Fires the engine starting event into the next handler in theEnginePipeline
chain. -
fireEngineStateChanged
void fireEngineStateChanged()Fires the engine state changed event into the next handler in theEnginePipeline
chain. The state change events occur after the engine starting event and generally signify that the engine has been shutdown normally. -
fireFailed
Fires theEngine
failed event into the next handler in theEnginePipeline
chain.- Parameters:
failure
- The exception that describes the conditions under which the engine failed.
-
fireRead
Fires a read of ProtonBuffer events into the previous handler in theEnginePipeline
for further processing.- Parameters:
buffer
- TheProtonBuffer
that carries the bytes read.
-
fireRead
Fires a read of HeaderFrame events into the previous handler in theEnginePipeline
for further processing.- Parameters:
header
- TheHeaderEnvelope
that carries the header bytes read.
-
fireRead
Fires a read of SASL events into the previous handler in theEnginePipeline
for further processing.- Parameters:
envelope
- TheSASLEnvelope
that carries the SASL performative read.
-
fireRead
Fires a read of IncomingProtocolFrame events into the previous handler in theEnginePipeline
for further processing.- Parameters:
envelope
- TheIncomingAMQPEnvelope
that carries the AMQP performative read.
-
fireWrite
Fires a write ofOutgoingAMQPEnvelope
events into the next handler in theEnginePipeline
for further processing.- Parameters:
envelope
- TheOutgoingAMQPEnvelope
that carries the AMQP performative being written.
-
fireWrite
Fires a write ofSASLEnvelope
events into the next handler in theEnginePipeline
for further processing.- Parameters:
envelope
- TheSASLEnvelope
that carries the SASL performative being written.
-
fireWrite
Fires a write of HeaderFrame events into the next handler in theEnginePipeline
for further processing.- Parameters:
envelope
- TheHeaderEnvelope
that carries the AMQP Header being written.
-
fireWrite
Fires a write of ProtonBuffer events into the next handler in theEnginePipeline
for further processing.- Parameters:
buffer
- TheProtonBuffer
that carries the bytes being written.ioComplete
- An optionalRunnable
callback that is signaled when the I/O completes successfully.
-


An alternatively spliced isoform of the Spi-B transcription factor.
Abstract
Spi-B is an Ets transcription factor related to the oncoprotein Spi-1/PU.1 and highly expressed in B lymphoid cells. The Ets proteins share a conserved Ets domain that mediates specific DNA binding. Spi-B binds DNA sequences containing a core 5'-GGAA-3 ' and activates transcription through this motif. Up to date, the biological function of Spi-B remains unknown. Here, we describe the characterization of an alternatively spliced variant of Spi-B, named deltaSpi-B, which has lost the Ets domain. In B lymphoid cells, deltaspi-B and spi-B mRNAs were present simultaneously in a ratio of around 10 %. DeltaSpi-B product was not able to bind DNA and was recovered in cytoplasmic cellular extracts. We raise the hypothesis that delta Spi-B might affect Spi-B function by recruiting factors involved in Spi-B activity.


After logging in, this is the page you will be rerouted to. Depending on your user type, context specific links will appear on the navagation bar. From these views, you will be able to access
these capabilities:
My Shifts: Create, view, edit, and delete shifts to list for trade, as well as view pending and approved trades.
Open Shifts: View shifts currently put up on the "market" by your coworkers, as well as being able to "accpet" that shift.
Schedule: View available to store managers to approve or reject employee trades.
Admin Panel: View available to administrators used to manage basic user functions such as user type, permissions, and store assignments.


COMP90041 ProjA Feedback: XXUSERNAMEXX
Program Presentation
Including: layout and style, readability, adherence to coding
expectations, general care and appearance.
The full marks for this section of marking are as follows, depending on
up to which stage you have completed.
- Stage 1 initial allocation, +0.5.
- Stage 2 initial allocation, +1.
- Stage 3 initial allocation, +2.
Deductions
Some subset of the following lines will be selected by the marker.
Deduct 0.5 marks for any two errors listed below.
- constants not in upper case;
- bad choices for method names;
- bad choices for variable names;
- excessive commenting;
- inconsistent bracket placement;
- inconsistent indentation;
- insufficient commenting;
- lack of whitespace (visual appeal);
- lines >100 chars;
- no authorship statement;
- use of magic numbers;
- other stylistic issue, if major then deduct 0.5 marks for this error alone;
Additions (included in total mark only
if marks lost within this first section)
- overall care and presentation, +0.5;
Other Comments from Marker
Structure and Approach
Including: decomposition in to methods, declaration of instance variables
at the appropriate locations,
choice of parameters to methods.
The full marks for this section of marking are as follows, depending on
up to which stage you have completed.
- Stage 1 initial allocation, +0.5.
- Stage 2 initial allocation, +1.5.
- Stage 3 initial allocation, +2.
Deductions
Some subset of the following lines will be selected by the marker.
Deduct 0.5 marks for any two errors listed below.
- duplicate code segments;
- main method too long or too complex;
- other methods too long or too complex;
- insufficient use of methods;
- overly complex algorithmic approach;
- unnecessary duplication/copying of data;
- overly complex method argument lists;
- other structural issue, if major then deduct 0.5 marks for this error alone;
- avoidance of non-static instance variables/methods, -1.0 for this error alone;
Other comments from marker:
Program execution
Including: compilation, execution on test data, output presentation
and readability.
Programs that do not compile in the test environment will lose all
marks in this section.
Be sure to verify your submission and check the output
before you say "finished" to yourself.
The full marks for this section of marking are as follows, depending on
up to which stage you have completed.
- Stage 1 initial allocation, +1.
- Stage 2 initial allocation, +3.5.
- Stage 3 initial allocation, +6.
Deductions
Some subset of the following lines will be selected by the marker.
- unnecessary warning messages in compilation, -0.5;
- grossly incorrect Stage 1 output on test1, -0.5;
- grossly incorrect Stage 1 output on test2, -0.5;
- grossly incorrect Stage 1 output on test3, -0.5;
- grossly incorrect Stage 2 output on test1, -0.5;
- grossly incorrect Stage 2 output on test2, -0.5;
- grossly incorrect Stage 2 output on test3, -0.5;
- somewhat incorrect Stage 3 output on test1, -0.5;
- (or) grossly incorrect Stage 3 output on test1, -1.0;
- somewhat incorrect Stage 3 output on test2, -0.5;
- (or) grossly incorrect Stage 3 output on test2, -1.0;
- somewhat incorrect Stage 3 output on test3, -0.5;
- (or) grossly incorrect Stage 3 output on test3, -1.0;
Late Penalty
If you make a late submission without having prior agreement from
the lecturer, one of these lines may also be uncovered by the lecturer.
- One day late, -2.0;
- Two days late, -4.0;
- Three days late, -6.0;
XXMARKXX
Overall comments from marker:
Assignment Marker: XXMARKERXX
If you have any questions regarding your mark, please contact the lecturer
Jianzhong Qi at jianzhong.qi@unimelb.edu.au


dhclient.conf
Section: File Formats (5)Index Return to Main Contents
NAME
dhclient.conf - DHCP client configuration fileDESCRIPTION
The dhclient.conf file contains configuration information for dhclient, the Internet Systems Consortium DHCP Client.The dhclient.conf file is a free-form ASCII text file. It is parsed by the recursive-descent parser built into dhclient. The file may contain extra tabs and newlines for formatting purposes. Keywords in the file are case-insensitive. Comments may be placed anywhere within the file (except within quotes). Comments begin with the # character and end at the end of the line.
The dhclient.conf file can be used to configure the behaviour of the client in a wide variety of ways: protocol timing, information requested from the server, information required of the server, defaults to use if the server does not provide certain information, values with which to override information provided by the server, or values to prepend or append to information provided by the server. The configuration file can also be preinitialized with addresses to use on networks that don't have DHCP servers.
PROTOCOL TIMING
The timing behaviour of the client need not be configured by the user. If no timing configuration is provided by the user, a fairly reasonable timing behaviour will be used by default - one which results in fairly timely updates without placing an inordinate load on the server.The following statements can be used to adjust the timing behaviour of the DHCP client if required, however:
The timeout statement
timeout time ;
The timeout statement determines the amount of time that must pass between the time that the client begins to try to determine its address and the time that it decides that it's not going to be able to contact a server. By default, this timeout is sixty seconds. After the timeout has passed, if there are any static leases defined in the configuration file, or any leases remaining in the lease database that have not yet expired, the client will loop through these leases attempting to validate them, and if it finds one that appears to be valid, it will use that lease's address. If there are no valid static leases or unexpired leases in the lease database, the client will restart the protocol after the defined retry interval.
The retry statement
retry time;
The retry statement determines the time that must pass after the client has determined that there is no DHCP server present before it tries again to contact a DHCP server. By default, this is five minutes.
The select-timeout statement
select-timeout time;
It is possible (some might say desirable) for there to be more than one DHCP server serving any given network. In this case, it is possible that a client may be sent more than one offer in response to its initial lease discovery message. It may be that one of these offers is preferable to the other (e.g., one offer may have the address the client previously used, and the other may not).
The select-timeout is the time after the client sends its first lease discovery request at which it stops waiting for offers from servers, assuming that it has received at least one such offer. If no offers have been received by the time the select-timeout has expired, the client will accept the first offer that arrives.
By default, the select-timeout is zero seconds - that is, the client will take the first offer it sees.
The reboot statement
reboot time;
When the client is restarted, it first tries to reacquire the last address it had. This is called the INIT-REBOOT state. If it is still attached to the same network it was attached to when it last ran, this is the quickest way to get started. The reboot statement sets the time that must elapse after the client first tries to reacquire its old address before it gives up and tries to discover a new address. By default, the reboot timeout is ten seconds.
The backoff-cutoff statement
backoff-cutoff time;
The client uses an exponential backoff algorithm with some randomness, so that if many clients try to configure themselves at the same time, they will not make their requests in lockstep. The backoff-cutoff statement determines the maximum amount of time that the client is allowed to back off, the actual value will be evaluated randomly between 1/2 to 1 1/2 times the time specified. It defaults to two minutes.
The initial-interval statement
initial-interval time;
The initial-interval statement sets the amount of time between the first attempt to reach a server and the second attempt to reach a server. Each time a message is sent, the interval between messages is incremented by twice the current interval multiplied by a random number between zero and one. If it is greater than the backoff-cutoff amount, it is set to that amount. It defaults to ten seconds.
LEASE REQUIREMENTS AND REQUESTS
The DHCP protocol allows the client to request that the server send it specific information, and not send it other information that it is not prepared to accept. The protocol also allows the client to reject offers from servers if they don't contain information the client needs, or if the information provided is not satisfactory.
There is a variety of data contained in offers that DHCP servers send
to DHCP clients. The data that can be specifically requested is what
are called DHCP Options. DHCP Options are defined in
dhcp-options(5).
The request statement
[ also ] request [ [ option-space . ] option ] [, ... ];
The request statement causes the client to request that any server responding to the client send the client its values for the specified options. Only the option names should be specified in the request statement - not option parameters. By default, the DHCPv4 client requests the subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-search, domain-name-servers, host-name, nis-domain, nis-servers, ntp-servers and interface-mtu options. The DHCPv6 client requests by default name-servers and domain-search. Note that if you enter a 'request' statement, you over-ride this default and these options will not be requested.
In some cases, it may be desirable to send no parameter request list at all. To do this, simply write the request statement but specify no parameters:
request;
In most cases, it is desirable to simply add one option to the request list which is of interest to the client in question. In this case, it is best to 'also request' the additional options:
also request domain-search, dhcp6.sip-servers-addresses;
The require statement
[ also ] require [ [ option-space . ] option ] [, ... ];
The require statement lists options that must be sent in order for an offer to be accepted. Offers that do not contain all the listed options will be ignored. There is no default require list.
require name-servers; interface eth0 { also require domain-search; } The send statement send { [ option declaration ] [, ... option declaration ]} The send statement causes the client to send the specified options to the server with the specified values. These are full option declarations as described in dhcp-options(5). Options that are always sent in the DHCP protocol should not be specified here, except that the client can specify a requested dhcp-lease-time option other than the default requested lease time, which is two hours. The other obvious use for this statement is to send information to the server that will allow it to differentiate between this client and other clients or kinds of clients.
DYNAMIC DNS
The client now has some very limited support for doing DNS updates when a lease is acquired. This is prototypical, and probably doesn't do what you want. It also only works if you happen to have control over your DNS server, which isn't very likely.Note that everything in this section is true whether you are using DHCPv4 or DHCPv6. The exact same syntax is used for both.
To make it work, you have to declare a key and zone as in the DHCP server (see dhcpd.conf(5) for details). You also need to configure the fqdn option on the client, as follows:
send fqdn.fqdn "grosse.fugue.com."; send fqdn.encoded on; send fqdn.server-update off; also request fqdn, dhcp6.fqdn;
The fqdn.fqdn option MUST be a fully-qualified domain name. You MUST define a zone statement for the zone to be updated. The fqdn.encoded option may need to be set to on or off, depending on the DHCP server you are using.
The do-forward-updates statement
do-forward-updates [ flag ] ;
If you want to do DNS updates in the DHCP client script (see dhclient-script(8)) rather than having the DHCP client do the update directly (for example, if you want to use SIG(0) authentication, which is not supported directly by the DHCP client, you can instruct the client not to do the update using the do-forward-updates statement. Flag should be true if you want the DHCP client to do the update, and false if you don't want the DHCP client to do the update. By default, the DHCP client will do the DNS update.
OPTION MODIFIERS
In some cases, a client may receive option data from the server which is not really appropriate for that client, or may not receive information that it needs, and for which a useful default value exists. It may also receive information which is useful, but which needs to be supplemented with local information. To handle these needs, several option modifiers are available.The default statement
default [ option declaration ] ;
If for some option the client should use the value supplied by the server, but needs to use some default value if no value was supplied by the server, these values can be defined in the default statement.
The supersede statement
supersede [ option declaration ] ;
If for some option the client should always use a locally-configured value or values rather than whatever is supplied by the server, these values can be defined in the supersede statement.
The prepend statement
prepend [ option declaration ] ;
If for some set of options the client should use a value you supply, and then use the values supplied by the server, if any, these values can be defined in the prepend statement. The prepend statement can only be used for options which allow more than one value to be given. This restriction is not enforced - if you ignore it, the behaviour will be unpredictable.
The append statement
append [ option declaration ] ;
If for some set of options the client should first use the values supplied by the server, if any, and then use values you supply, these values can be defined in the append statement. The append statement can only be used for options which allow more than one value to be given. This restriction is not enforced - if you ignore it, the behaviour will be unpredictable.
LEASE DECLARATIONS
The lease declaration
lease { lease-declaration [ ... lease-declaration ] }
The DHCP client may decide after some period of time (see PROTOCOL TIMING) that it is not going to succeed in contacting a server. At that time, it consults its own database of old leases and tests each one that has not yet timed out by pinging the listed router for that lease to see if that lease could work. It is possible to define one or more fixed leases in the client configuration file for networks where there is no DHCP or BOOTP service, so that the client can still automatically configure its address. This is done with the lease statement.
NOTE: the lease statement is also used in the dhclient.leases file in order to record leases that have been received from DHCP servers. Some of the syntax for leases as described below is only needed in the dhclient.leases file. Such syntax is documented here for completeness.
A lease statement consists of the lease keyword, followed by a left curly brace, followed by one or more lease declaration statements, followed by a right curly brace. The following lease declarations are possible:
bootp;
The bootp statement is used to indicate that the lease was acquired using the BOOTP protocol rather than the DHCP protocol. It is never necessary to specify this in the client configuration file. The client uses this syntax in its lease database file.
interface "string";
The interface lease statement is used to indicate the interface on which the lease is valid. If set, this lease will only be tried on a particular interface. When the client receives a lease from a server, it always records the interface number on which it received that lease. If predefined leases are specified in the dhclient.conf file, the interface should also be specified, although this is not required.
fixed-address ip-address;
The fixed-address statement is used to set the ip address of a particular lease. This is required for all lease statements. The IP address must be specified as a dotted quad (e.g., <IP_ADDRESS>).
filename "string";
The filename statement specifies the name of the boot filename to use. This is not used by the standard client configuration script, but is included for completeness.
server-name "string";
The server-name statement specifies the name of the boot server name to use. This is also not used by the standard client configuration script.
option option-declaration;
The option statement is used to specify the value of an option supplied by the server, or, in the case of predefined leases declared in dhclient.conf, the value that the user wishes the client configuration script to use if the predefined lease is used.
script "script-name";
The script statement is used to specify the pathname of the dhcp client configuration script. This script is used by the dhcp client to set each interface's initial configuration prior to requesting an address, to test the address once it has been offered, and to set the interface's final configuration once a lease has been acquired. If no lease is acquired, the script is used to test predefined leases, if any, and also called once if no valid lease can be identified. For more information, see dhclient-script(8).
vendor option space "name";
The vendor option space statement is used to specify which option space should be used for decoding the vendor-encapsulate-options option if one is received. The dhcp-vendor-identifier can be used to request a specific class of vendor options from the server. See dhcp-options(5) for details.
medium "media setup";
The medium statement can be used on systems where network interfaces cannot automatically determine the type of network to which they are connected. The media setup string is a system-dependent parameter which is passed to the dhcp client configuration script when initializing the interface. On Unix and Unix-like systems, the argument is passed on the ifconfig command line when configuring the interface.
The dhcp client automatically declares this parameter if it uses a media type (see the media statement) when configuring the interface in order to obtain a lease. This statement should be used in predefined leases only if the network interface requires media type configuration.
renew date;
rebind date;
expire date;
The renew statement defines the time at which the dhcp client should begin trying to contact its server to renew a lease that it is using. The rebind statement defines the time at which the dhcp client should begin to try to contact any dhcp server in order to renew its lease. The expire statement defines the time at which the dhcp client must stop using a lease if it has not been able to contact a server in order to renew it.
These declarations are automatically set in leases acquired by the DHCP client, but must also be configured in predefined leases - a predefined lease whose expiry time has passed will not be used by the DHCP client.
Dates are specified in one of two ways. The software will output times in these two formats depending on if the db-time-format configuration parameter has been set to default or local.
If it is set to default, then date values appear as follows:
<weekday> <year>/<month>/<day>
<hour>:<minute>:<second>
The weekday is present to make it easy for a human to tell when a lease expires - it's specified as a number from zero to six, with zero being Sunday. When declaring a predefined lease, it can always be specified as zero. The year is specified with the century, so it should generally be four digits except for really long leases. The month is specified as a number starting with 1 for January. The day of the month is likewise specified starting with 1. The hour is a number between 0 and 23, the minute a number between 0 and 59, and the second also a number between 0 and 59.
If the db-time-format configuration was set to local, then the date values appear as follows:
epoch <seconds-since-epoch>; # <day-name> <month-name>
<day-number> <hours>:<minutes>:<seconds> <year>
The seconds-since-epoch is as according to the system's local clock (often referred to as "unix time"). The # symbol supplies a comment that describes what actual time this is as according to the system's configured timezone, at the time the value was written. It is provided only for human inspection, the epoch time is the only recommended value for machine inspection.
Note that when defining a static lease, one may use either time format one wishes, and need not include the comment or values after it.
If the time is infinite in duration, then the date is never instead of an actual date.
ALIAS DECLARATIONS
alias { declarations ... }
Some DHCP clients running TCP/IP roaming protocols may require that in addition to the lease they may acquire via DHCP, their interface also be configured with a predefined IP alias so that they can have a permanent IP address even while roaming. The Internet Systems Consortium DHCP client doesn't support roaming with fixed addresses directly, but in order to facilitate such experimentation, the dhcp client can be set up to configure an IP alias using the alias declaration.
The alias declaration resembles a lease declaration, except that options other than the subnet-mask option are ignored by the standard client configuration script, and expiry times are ignored. A typical alias declaration includes an interface declaration, a fixed-address declaration for the IP alias address, and a subnet-mask option declaration. A medium statement should never be included in an alias declaration.
OTHER DECLARATIONS
db-time-format [ default | local ] ;
The db-time-format option determines which of two output methods are used for printing times in leases files. The default format provides day-and-time in UTC, whereas local uses a seconds-since-epoch to store the time value, and helpfully places a local timezone time in a comment on the same line. The formats are described in detail in this manpage, whithin the LEASE DECLARATIONS section.
reject cidr-ip-address [, ... cidr-ip-address ] ;
The reject statement causes the DHCP client to reject offers from servers whose server identifier matches any of the specified hosts or subnets. This can be used to avoid being configured by rogue or misconfigured dhcp servers, although it should be a last resort - better to track down the bad DHCP server and fix it.
The cidr-ip-address configuration type is of the form ip-address[/prefixlen], where ip-address is a dotted quad IP address, and prefixlen is the CIDR prefix length of the subnet, counting the number of significant bits in the netmask starting from the leftmost end. Example configuration syntax:
reject <IP_ADDRESS>/16, <IP_ADDRESS>;
The above example would cause offers from any server identifier in the entire RFC 1918 "Class C" network <IP_ADDRESS>/16, or the specific single address <IP_ADDRESS>, to be rejected.
interface "name" { declarations ... }
A client with more than one network interface may require different behaviour depending on which interface is being configured. All timing parameters and declarations other than lease and alias declarations can be enclosed in an interface declaration, and those parameters will then be used only for the interface that matches the specified name. Interfaces for which there is no interface declaration will use the parameters declared outside of any interface declaration, or the default settings.
Note well: ISC dhclient only maintains one list of interfaces, which is either determined at startup from command line arguments, or otherwise is autodetected. If you supplied the list of interfaces on the command line, this configuration clause will add the named interface to the list in such a way that will cause it to be configured by DHCP. Which may not be the result you had intended. This is an undesirable side effect that will be addressed in a future release.
pseudo "name" "real-name" { declarations ... }
Under some circumstances it can be useful to declare a pseudo-interface and have the DHCP client acquire a configuration for that interface. Each interface that the DHCP client is supporting normally has a DHCP client state machine running on it to acquire and maintain its lease. A pseudo-interface is just another state machine running on the interface named real-name, with its own lease and its own state. If you use this feature, you must provide a client identifier for both the pseudo-interface and the actual interface, and the two identifiers must be different. You must also provide a separate client script for the pseudo-interface to do what you want with the IP address. For example:
interface "ep0" { send dhcp-client-identifier "my-client-ep0"; } pseudo "secondary" "ep0" { send dhcp-client-identifier "my-client-ep0-secondary"; script "/etc/dhclient-secondary"; }
The client script for the pseudo-interface should not configure the interface up or down - essentially, all it needs to handle are the states where a lease has been acquired or renewed, and the states where a lease has expired. See dhclient-script(8) for more information.
media "media setup" [ , "media setup", ... ];
The media statement defines one or more media configuration parameters which may be tried while attempting to acquire an IP address. The dhcp client will cycle through each media setup string on the list, configuring the interface using that setup and attempting to boot, and then trying the next one. This can be used for network interfaces which aren't capable of sensing the media type unaided - whichever media type succeeds in getting a request to the server and hearing the reply is probably right (no guarantees).
The media setup is only used for the initial phase of address acquisition (the DHCPDISCOVER and DHCPOFFER packets). Once an address has been acquired, the dhcp client will record it in its lease database and will record the media type used to acquire the address. Whenever the client tries to renew the lease, it will use that same media type. The lease must expire before the client will go back to cycling through media types.
bootp-broadcast-always;
The bootp-broadcast-always statement instructs dhclient to always set the bootp broadcast flag in request packets, so that servers will always broadcast replies. This is equivalent to supplying the dhclient -B argument, and has the same effect as specifying 'always-broadcast' in the server's dhcpd.conf. This option is provided as an extension to enable dhclient to work on IBM s390 Linux guests.
SAMPLE
The following configuration file is used on a laptop running NetBSD 1.3. The laptop has an IP alias of <IP_ADDRESS>, and has one interface, ep0 (a 3com 3C589C). Booting intervals have been shortened somewhat from the default, because the client is known to spend most of its time on networks with little DHCP activity. The laptop does roam to multiple networks.
timeout 60; retry 60; reboot 10; select-timeout 5; initial-interval 2; reject <IP_ADDRESS>; interface "ep0" { send host-name "andare.fugue.com"; send dhcp-client-identifier 1:0:a0:24:ab:fb:9c; send dhcp-lease-time 3600; supersede domain-search "fugue.com", "rc.vix.com", "home.vix.com"; prepend domain-name-servers <IP_ADDRESS>; request subnet-mask, broadcast-address, time-offset, routers, domain-search, domain-name, domain-name-servers, host-name; require subnet-mask, domain-name-servers; script "/sbin/dhclient-script"; media "media 10baseT/UTP", "media 10base2/BNC"; } alias { interface "ep0"; fixed-address <IP_ADDRESS>; option subnet-mask <IP_ADDRESS>; }This is a very complicated dhclient.conf file - in general, yours should be much simpler. In many cases, it's sufficient to just create an empty dhclient.conf file - the defaults are usually fine.
SEE ALSO
dhcp-options(5), dhcp-eval(5), dhclient.leases(5), dhcpd(8), dhcpd.conf(5), RFC2132, RFC2131.AUTHOR
dhclient(8) was written by Ted Lemon under a contract with Vixie Labs. Funding for this project was provided by Internet Systems Consortium. Information about Internet Systems Consortium can be found at https://www.isc.org.
Index
- NAME
- DESCRIPTION
- PROTOCOL TIMING
- LEASE REQUIREMENTS AND REQUESTS
- DYNAMIC DNS
- OPTION MODIFIERS
- LEASE DECLARATIONS
- ALIAS DECLARATIONS
- OTHER DECLARATIONS
- SAMPLE
- SEE ALSO
- AUTHOR
This document was created by man2html, using the manual pages.
Time: 05:33:59 GMT, December 24, 2015


Agenda for Day
===========
9:00am Application of V4 architecture in High Level Applications Bob Dalesio
9:15 am interoperaboility V3 V4 Marty Kraimer
10:00 am Use of V3Channel for Gas Analyser at Diamond, David Hickin
10:15 break
10:30 am Beam line requirements for scanning, data acquisition, and analysis, Daron Chabot.
11:00 am synApps, record types and data. Tim Mooney.
11:30 am Use of areaDetector and synApps for biological data analysis. John Skinner
12:00 noon Scan system for experiments at SNS. Kay Kasemir
12:30-1:30 lunch
snuck in talk: PXdb, John
1:30-3:00 pm Version 4 IOC planning to support beamline controls. Discussion. Bob Dalesio.
3:30 – 4;00 break
4:00 – 4:30pm Normative Types review. *Greg*
* EPICS URI. Review of use of the EPICS URL. *Greg*
4:30pm – 5:00 Proposal for "editing down" and implementation of N-types *Michael*
*****
NEW TOPIC: Application of V4 architecture in High Level Applications, Bob Dalesio
*****
Talk presentation Powerpoint at: http://epics-pvdata.sourceforge.net/talks/2012/V4EPICSKorea20121023.ppt
Gave a summary of how EPICSV4 is adding facilities for building data services. Showed for beamline
experimenters, where in their experimental control system EPICS V4 service would fit and what they
might do.
*****
NEW TOPIC: interoperaboility V3 V4, Marty Kraimer
*****
See sections Overview of iocCore, pvAccess and pvIOC at:
http://epics-pvdata.sourceforge.net/talks/2012/pvIOCCPP.html#overview_of_ioccore,_pvaccess_and_pvioc
and section
CAV3/V3Record <==> pvIOC/pvAccess :
http://epics-pvdata.sourceforge.net/talks/2012/pvIOCCPP.html#cav3/v3record_<==>_pvioc/pvaccess
*****
NEW TOPIC: Using V3Channel at Diamond, David Hickin
*****
Showed how you change a V3 IOC boot script, dbd file, and its makefile to add v3channel.
Then he used an example of using pvput (with pvaccess on the wire), to write to
a V4 scalar, attached to a V3 channel on the IOC.
He then showed monitoring (pvget -m) a V4 array, which in the IOC is attached to
a V3 waveform.
Scribe: Brilliant!
******
NEW TOPIC: Beam line requirements for scanning, data acquisition, and analysis, Daron Chabot.
******
See talk at: http://epics-pvdata.sourceforge.net/talks/2012/bnl_10_18_12.pdf
Next generation detectors are of order 1-4 Mpix@s-24 kHz. == 40 Gbps. Another example: LBNL FastCCD 2 Mpix @ 2.2 kHz = 6.4 Gbps.
For X-ray Photon Correlation Spectroscopy (a common technique) people are looking to
analyze 40-60,000 frames per second and making correlations between frames.
So, presently it takes only 1 or 2 sconds to take the data.
Then presently the pre processing of the images (which detemines whether there was anything interesting in the data) takes about 15-60 mins. They want to get that down to seconds.
Things V3 is missing for beamlines
* A way of managing data that is represented in Reciprocal Space (a coordinate transform of the data), which is common for beamline physics. A system which maps coordinate space to reciprocal space.
* "Asynchronous timestamps" - where the time at which data was taken is attached to the data after the fact. That is, event reconstruction. This functionality is common in particle physics, but isn't native to EPICS or have a well known pattern.
* A native data manager. Something like pvManager operating server side as a service. "Decoupling the rate of events on the network from the rate of refresh needed by the client".
http://pvmanager.sourceforge.net
* A framework for "fly scanning" (scanning a number of dependent variables against time - the independent variable needs no settle time).
GW: Are you talking about a client side program like a "correlation Plots"?
DC: Yes, that would be great.
Summary:
* New detectors pose a challenge
* SW must permit interactive "exploration" for data acquisition and analysis. Too allow experimenters to
interactively try different frame rates, triggering times etc. Need a flexible tool that allows one
to configure an experminetal setup and change it ad hoc.
* No single person can meet the challenges, collaboration is requried.
******
NEW TOPIC: synApps, Epics Software for beamline controls, Tim Mooney
******
SynApps is a collection of EPICS modules for synchrotron beamlines.
Oriented to beamline control, not experiment control
Modules:
areaDetector: CCD detector support. Supports 2-d detectors. areaDetector includes a plugin mech. for
grabbing the detector device data, and assemble a data file + eg the conditions under which data was taken.
Importantly it takes images of the disk, and puts them into EPICS Pvs.
It operates in the range of up to 100Hz.
autoSave module:
Records the latest values of selected EPICS Pvs; restores those values when the IOC restarts.
busy module:
Allows Ca clients, and asyn threads, to complete put_callback operations.
Eg, SNL prog driven by EPICS PVs.
Scan sw in synapps is absolutely reliant on thsi module, because without it it wouldn't know when to execute the callback.
calc module:
Evaluates expressions entered at runtime. Hence sequence of operations.
When doing a scan that involves a motor and scanners, the calc module is what is controlling the sequence.
dxp module
Important for acquiring spectra
UC is focusing down to a small point, and then raster scanning.
Is central to method for storing spectra for each pixel
Streams to disk for fly scans.
mca module:
Used for step scans (as opposed to fly scans)
motor module
For controlling the "manual" move of a motor - which is out of scope for the motor record.
For instance, if you want N (<8 or so) motors to each be at a given position at a given time.
Uses motor record.
stepper and servo motors
soft-motor support
user/dial/raw coordinates
pre/post move commands
etc..
Trajectory support built in for some motors.
optics module
Supports slits and mirrors, and monochromaters
Aslo low E monochrometers
Supports optics table
quadEM module
Support for 4-input electrometers
softGlue module
Support for end-user programmable glue electronics
Applications:
Simple glue electronics problems, where otherwise you may have had to use a breadboard.
Fly scans
Pump-probe experiments
Implement smart oscilloscope trigger for eg diagnostics
Drives EPICS record processing from hardware input
Works with microline off the shelf FPGAs
sscan module
Allows for expression and acquisition of 1-d correlation experiments.
The issue for it, is that storing previously configured scan records for later retrieval and
reuse, has no well established pattern or user level support.
SynApps in Context
It is suff. for many types of experminent
Wanted:
There are too many expermient types to develop a custom client for each.
So, need generic tools from which to build experiment controls.
Ideally "do for experiments what EPICS does for beamlines."
SynApps is used with "spec". Spec is the standard progrm used by materials scientists for controlling experiments. It does not do analsysis. So, the common UC would be control eg a crystallography experiment with spec, and use the synApps sscan record to read results.
Discussion
TM wants to give experimenters what EPICS did for beamline.
Not clear what that means
python wrapper for the client seems the only obvious thing.
session ends 12:40
AFTERNOON
==========
NEW TOPIC: Scan system for experiments at SNS. Kay Kaswemir
KK described a CSS client and server side suport, for scanning.
Scans are confirgured in the GUI, or by hand in XML. Once the scan is configured,
it is submitted (by java RMI) to the scan server which executes it and returns results.
The scan server does not wrap sscan record, it implements its own scan engine.
The architectural premise is that one beamline experminent would use one scan server.
One scan server presently only (deliberately) executes one scan request at a time.
So, it's oriented toward helping beamline scientists graphically set up their experimanent
in CSS, then run it remotely in the experminetal beamline, possibly lasting a long time (hrs or days)
[gw: It's not so much oriented toward accelerator physics, where one might well set 100s of
dependent variables, but acquiring relatively slowly, and one doen't have want to or need to
write a script to make the scan.
Since it's java, an acquisition script can be written in matlab!
GW: very cool for beamline experminents. Probably not so pertinent for accel. phyics.
TM: How do I get this system and deploy it?
KK: It's packaged as a CSS [ie an eclipse] plugin. You build your scanner as an Eclipse "product"
using the CSS Scan "feature".
******
NEW TOPIC: PXdb, Rick Buono
******
Is a Protien Crystalography Database.
Written in perl, javascript, on a postgress db.
PXdb is used by visiting scientists, to
request beamtime
manage groups, projects, crystals
Review details of all tehir data collections
Generate summary reports
Utilized by BNL staff to
Administer BNL hosted and remote experiment scheduling and execution.
******
NEW TOPIC: CBASS experimental data setup
******
CBASS is a beamline experiment platform by BNL.
It uses EPICS, on RTEMS, EPICS SoftIOCs
It's essentially 3-layer model, where the servers are implemented.
It's python on server side. The GUI is tkl/TK
******
NEW TOPIC: Formulating the Remit of the EPICS V4 Working Group for the next year.
******
Discussion led by BD.
BD comments that there were 2 levels of participation in the first WG:
- Participant - at least 20-30% of your time
- Observer. Makes comments on the work of the group.
We'd love Tim and others to be at least observer.
BD starts listing service we might work on:
Potential Projects of Next Working Group Charter:
* pvIOC should understand multi-core processors, and matrix manipulation, recording the time sequence from hardware.
* NDArray support - areaDetector. Normalizing areaDetector using Normative Types
* Image Library - tools for manipulating images and packaging as NTImage
* Diamond had the following specific requirements:
DH (on behalf of JR):
Want monitors suitable for data acquisition. Must guarantee in-order delivery and configurable queue size and replacement policy on overflow (drop newest or drop oldest etc). May already exist, want to develop test app (ethercat or areadetector)
DH (on behalf of Tom Cobb):
Want to be able to run an areaDetector driver on one machine, and an areaDetector plugin on another machine, and transfer the NDArrays between the two using EPICS V4 monitors
DH (on behalf of Tom Cobb):
Want to have an existing areaDetector driver (like simDetector) be connected to a V4 record layer so that it dynamically created fields according to the underlying parameter library, and to do it with only header file changes to the driver.
* Client Applications. Replacement for (m)edm
* Scan service
* Experimental data environment logging
* Coordinate space conversion library
* Analysis library
GW: The above projects and requirements do not seem perculiar to beamline physics, they're really applicable also to accelerator physics.
GW: Also, many of them are still quite etherial, not closely defined. But to be a goal of a collaboration, a goal must be very concrete.
So, suggest not explicitly orienting the next WG toward beamline physics, but rather taking only those requirements above
which are conrete, and doing those within the existing context of the WG.
Consensus agrees.
Conclusion: the next charter of the WG will be oriented towards accelerator and bealine physics support jointly. We won't specifically orient one WG to beamline physics, and another to accelerator phyics.
Meeting ends, 17:00