Sets the constraint to apply to this node's transform before applying the parent transform. Using constraints without a parent may have unexpected results.
A name that's applied to the node in the monitor and other tools. This name has no effect at runtime.
This is the ID of the DOM element that is created as the parent of the component. It is used to reference other nodes in the gadget. If it is specified, it must be unique within the gadget.
Set this prop to be notified when the node is assigned its endpoint address. This is not necessary for most nodes.
Sets the specified node as the parent of this transform. The endpoint address for the parent node can be in any gadget.
If the parent node is not valid, this node and its children will not be traversed.
An alias for debugName.
The rotation around the X axis (pitch) to apply to all children. If rotation is specified as a quaternio, this must be undefined.
The rotation around the Y axis (yaw) to apply to all children. If rotation is specified as a quaternio, this must be undefined.
The rotation around the Z axis (roll) to apply to all children. If rotation is specified as a quaternio, this must be undefined.
The rotation to apply to all children, specified as a quaternion.
The scale on the X axis to apply to all children. Must be left undefined if uniformScale is specified.
The scale on the Y axis to apply to all children. Must be left undefined if uniformScale is specified.
The scale on the Z axis to apply to all children. Must be left undefined if uniformScale is specified.
Applies an already-constructed AvNodeTransform to the transform. If this prop is set, all other properties will replace the matching components of this transform.
The translation on the X axis to apply to all children.
The translation on the Y axis to apply to all children.
The translation on the Z axis to apply to all children.
The uniform scale to apply to all children. If uniformScale is specified, scaleX, scaleY, and scaleZ must be undefined.
Controls whether or not this node and its children are visible. If retaining the state of a node is important as it comes and goes, use the visible prop instead of omitting the node from the render function. This allows the renderer to retain the node's state even when you don't want it to draw.
Generated using TypeDoc
Props for AvTransform


Francesco Gadaleta has more than 15 years experience in computer programming and algorithm
design. He graduated in computer engineering from Politecnico di Milano, Italy where he developed
novel analytical methods to detect breast cancer (BRCA1/2).
He has a PhD in Computer Science from University KU Leuven where he designed novel security
techniques with virtualization technology (hypervisor).
He was member of the advanced analytics team of Johnson&Johnson.
He currently hosts podcast
datascienceathome,
the podcast that "makes artificial intelligence easy for everyone".
Francesco graduated as Techstars Alumni, participating to the Techstars Accelerator at Barclays 2017
in Cape Town, South Africa, as the Chief Data Officer of startup Abe.ai


--- layout: page title: FreeRADIUS 'man' pages subtitle: Documentation from the server subpage: true navorder: 200 hero: documentation subnav: - text: Programs link: '/radiusd/man/#programs' - text: Configuration Files link: '/radiusd/man/#files' - text: Modules link: '/radiusd/man/#modules' ---
For example, some NAS boxes send a NAS-Port attribute which is a 32-bit number composed of port, card, and interface, all in different bytes. To see these attributes split into pieces, you can have an entry in the 'users' file like:
DEFAULT
Vendor-Interface = `%{expr: %{NAS-Port} / (256 * 256)}`,
Vendor-Card = `%{expr: (%{NAS-Port} / 256) %% 256}`,
Vendor-Port = `%{expr: %{NAS-Port} %% 256}`
where the attributes Vendor-Interface, Vendor-Card, and Vendor-Port are attributes created by either you or a vendor-supplied dictionary.
The methematical operators supported by the expression module are:
NOTE: The modulo remainder operator is '%%', and not '%'. This is due to the '%' character being used as a special character for dynamic translation.
NOTE: These operators do NOT have precedence. The parsing of the input string, and the calculation of the answer, is done strictly left to right. If you wish to order the expressions, you MUST group them into sub-expression, as shown in the previous example.
All of the calculations are performed as unsigned 32-bit integers.
modules { ...
expr {
}
...
}
...
instantiate { ...
expr ...
}


{% include 'resources.html' %}
{% include 'nav.html' %}
Card Name:
Filter By Color:
White
Blue
Black
Red
Green
Filter By CMC:
=
Filter By Power:
=
Filter By Toughness:
=
Clear Filter
Submit
{% if cards == 'error' %}
Error Searching for Cards
{% else %} {% for n in cards %}
{{n[0]}}
{% endfor %} {% endif %}


Based on profile '{{model.contract.profileId.toLowerCase()}}'
Created by {{model.contract.createdBy}} at {{model.contract.createdAt}}
Offered by {{model.contract.offeredBy}} at {{model.contract.offeredAt}}
Accepted by {{model.contract.acceptedBy}} at {{model.contract.acceptedAt}}
Approved by {{model.contract.approvedBy}} at {{model.contract.approvedAt}}
Cache hit: {{ model.cacheHit }}, backend
loaded in {{ model.loadedInMs }}ms
|}{! we can use "state" or "contractState" - see graphQl mapping in request below !}{|
Offer draft
resync
|}{! TODO add a text field where the user can justify this !}{|
Approve contract


Omega Psi Phi was founded on November 17, 1911, at Howard University in Washington, D.C. The founders were three Howard University undergraduates, -- Edgar Amos Love, Oscar James Cooper and Frank Coleman. Joining them was their faculty adviser, Dr. Ernest Everett Just.
Get Started!send us an email and we will get back to you as soon as possible!
123-456-6789


Hello!
I've a question. If I get an RMS voltage (sum of squares, and sqrt) proportional to the AC current (using YHDC CT) - how to do I turn this into a AC current...? I am using a 100R resistor to give a 0-35amp scale based on 2.5v bias, and 5v max.
There doesn't appear to be a direct multiplication which works, i.e. peak of 2.5v x 14.14 gives 35amps, but this doesn't work.
I've obviously missed something....
James
Re: RMS and math question
Provided that you are using a pure resistance, Ohms Law works just the same with alternating rms average values of voltage and current as it does for direct voltages and currents.
But I'm struggling to understand the real question that you are asking. Is it how to choose a burden resistor? Is that what your 100 Ω resistor is?
Have you looked here?
Re: RMS and math question
Hiya Robert,
Thanks for the reply. I have built the circuit as described in your link, and have a 100R as a burden resistor. I was doing the code the simple way - i.e. read the maximum voltage, subtract the bias (2.5v) and then multiply to get an amps reading - as the voltages were proportional to the amps.
I've updated that code to use the RMS method as in the emmonlib code, and I get a voltage back - just can't get my head around how to convert it into an amps. I can't see in the emmonlib any conversion code - i.e. rms volts x 2 = amps.
James
Re: RMS and math question
It is the burden resistor that converts current to voltage, not the other way round. The current transformer is just that - it works on currents, so you need to switch your thinking round a little when dealing with c.t's.
You have a primary current of 35 A, you say. Let's assume you are using the YHDC SCT-013-000 which has a ratio of 100 A : 50 mA (a current transformer's ratio is always given in Amps). Therefore, it will generate a secondary current of 35 / 100 × 50 mA = 17.5 mA. That current will flow in the burden resistor and generate a voltage of 17.5 mA × 100 Ω = 1.75 V.
Because we have been dealing with rms values so far, this is the rms value. For a sine wave only (not quite true but true in practice) , the peak-peak value is 2√2 × the rms value, so your peak-peak voltage is 4.95 V. So that's just about OK for a 5 V range at the ADC input.
Going back a stage, the rms voltage is 1.75 V and you get 1024 counts per 5 V. Therefore the count (rms value - why not? !) is 1.75 / 5 × 1024 = 358.4
So now you know that 35 A gives you 358.4 counts, given that c.t. and burden resistor.
All I've actually done there is work through the input circuit quite logically. You have read CT and AC power adaptor installation and calibration theory, haven't you? In there, you'll see how all that relates to the calibration constant that is fed into the methods of emonLib.
Re: RMS and math question
Hiya Robert,
I had read the pages on this site many times, but obviously not that page well enough. Your worked example is most helpful.
I'll implement this tonight and see if that sorts it.
Many thanks,
James
Re: RMS and math question
Hiya Robert,
Code updated, bugs fixed and that is working nicely now.
Very many thanks for your help!
James


"I am basically ABAP Application Developer with 3years of SAP Technical Exposure.
Brilliant Grammar High School, Hyderabad
Percentage: 93%
Narayana Junior College, Nellore
Percentage: 97.4%
JNT University, Tirupathi, India.
Graduated: Apr 2013
Percentage: 83%
Worked as SAP ABAP developer in various projects with Johnson & Johnson Client.
Project DetailsWorking as ABAP developer, developing various internal tools required for AOF team in SAP
Project Details| Name | Sneha Vadhi |
| Address | Sri Sai PG,Opp to CMRIT, Kundanahalli, Bangalore-560037 |
|<EMAIL_ADDRESS>| |
| Phone | +91<PHONE_NUMBER> |


A specification system (spec) ensures that data that is passed in conforms to the requirements.
perusal-immutable
implements a performant spec system for Javascript - users can define custom specifications, and verify that data satisfies the provided specification. Pairs well with Immutable.js to improve speed by retaining metadata on the passing/failing specs.
Inspired by Clojure's spec/alpha.
// Invalid validity checking returns false.
isValid(1, even); // false
// Valid values returns true.
isValid(2, even); // true
// We can define our own specifications.
define('is-a?', new Pred("is 'a'?", (value) => value === 'a'));
isValid('b', 'is-a?'); // false
isValid('a', 'is-a?'); // true
// We can join multiple predicates.
// Note that the definition key does not have to be the same as the explanatory string.
define('pos-even', and('positive, even number', positive, even));
isValid(2, 'pos-even'); // true
isValid(-2, 'pos-even'); // false
// We can also check maps.
const point = {
x: 1,
y: 2,
};
const threeDpoint = new Map({
x: 1,
y: 2,
z: 3,
});
define('point', keys('2d or 3d point', {x: isNumber, y: isNumber, z: optional(isNumber)}));
define('point or string', or('point or string', getSpec('point'), isString));
isValid(point, 'point'); // true
explain(point, 'point');
/*
Value:
{ x: 1, y: 2 }
Passes specification 2d or 3d point.
*/
isValid(threeDpoint, 'point'); // true
isValid(threeDpoint, 'point or string'); // true
More examples can be found in example.js
.
Node
> npm install perusal-immutable
Yarn
> yarn add persual-immutable
Refer to the online documentation at https://walnutdust.github.io/perusal-immutable.
TL;DR: Specs provide run-time analysis and verification of the data structure with flexibility although at the cost of (some) run-time performance and the lack of compiler help.
For more information, see the FAQ.
Definitions:
perusal-immutable
should operate with good performance guarantees.perusal-immutable
should be readable without being cumbersome.perusal-immutable
should enforce good behavior, not force users to work around it.Static typing is used by programmers to help them reason about the program. Specifically, static typing offers the following benefits:
Specs, on the other hand, performs run-time verification on the data, which offers:
Refer to Clojure's spec guide to see how people smarter than me reason about this.
Definitely! Clojurescript already a spec library.
However, Clojurescript performs this checking from fresh as we build up a data structure, leading to unnecessary repetition of checks which may be costly. See the next question for benchmarks!
If we were only doing dynamic type checking via typeof
, it takes only about ~1% more time, and scales linearly. For more complex arguments it is harder to argue about it, but note that most programs do end up explicitly checking inputs in some form or the other, be it nullable checks, or whether the input asserts to a certain usable specification. In those cases, perusal-immutable
helps formalise the code, and offers programmers the capacity to say that given a input that satisfies a certain spec, there will always be output of a certain spec?
To further improve performance, perusal-immutable
also offers an immutable version of itself, which wraps immutable data types from immutable.js
with metadata that tracks the specs that a certain object has fulfilled. In this manner, if the programmer strictly uses the provided wrappers, we skip repetitive checking and get a huge performance boost if the same data is used in multiple areas.
Benchmarks
Simple Type Checking
const {performance} = require('perf_hooks');
const n = 100000000;
let test;
const t0 = performance.now();
for (let i = 0; i < n; i++) {
test = 'test';
}
const t1 = performance.now();
console.log('Declaring a string took ' + (t1 - t0) / n + ' milliseconds on average.');
// Declaring a string took 8.706519499421119e-7 milliseconds on average.
const t2 = performance.now();
for (let i = 0; i < n; i++) {
typeof 'test' === 'string';
}
const t3 = performance.now();
console.log('Checking string type took ' + (t3 - t2) / n + ' milliseconds on average.');
console.log('Checking a string took ' + ((t3 - t2) / (t1 - t0)).toPrecision(3) + '% more time.');
const n = 10000000;
const t0 = performance.now();
for (let i = 0; i < 10000000; i++) {
typeof 'test' === 'string';
}
const t1 = performance.now();
console.log('Checking string type took ' + (t1 - t0) / n + ' milliseconds on average.');
// Checking string type took 8.643735998868942e-7 milliseconds on average.
// Checking a string took 0.993% more time.
Imutable types usage performance boost
Javascript
// Explanation works well with nesting too
const nestedPoint = new Map({
x: new Map({
x: new Map({
x: 2,
y: 3,
}),
}),
});
define('2-nested point', keys('nested nested point', {
x: keys('nested point', {x: getSpec('point')}),
}));
isValid(nestedPoint, '2-nested point'); // true
// A good way to capture the same behavior is via the immutable from JS method.
const nestedPoint2 = fromJS({
x: {
x: {
x: 2,
y: 3,
},
},
});
isValid(nestedPoint2, '2-nested point'); // true
// This works with normal JS Maps as well.
const nestedPoint3 = {
x: {
x: {
x: 2,
y: 3,
},
},
};
isValid(nestedPoint3, '2-nested point'); // true
// Test 1: Simple JS Maps
let start,
end,
numTimes = 10000000;
start = performance.now();
for (let i = 0; i < numTimes; i++) {
isValid(nestedPoint3, '2-nested point');
}
end = performance.now();
console.log(
'Test 1: Time taken to perform ' +
numTimes +
' validity checks on the JS Map is ' +
(end - start) +
'ms, averaging ' +
(end - start) / numTimes +
'ms.'
);
/* Test 1: Time taken to perform 10000000 validity checks on the JS Map is 5441.707319021225ms, averaging 0.0005441707319021225ms. */
// Test 2: fromJS (immutableJS) Map
start = performance.now();
for (let i = 0; i < numTimes; i++) {
isValid(nestedPoint2, '2-nested point');
}
end = performance.now();
console.log(
'Test 2: Time taken to perform ' +
numTimes +
' validity checks on the fromJS Map is ' +
(end - start) +
'ms, averaging ' +
(end - start) / numTimes +
'ms.'
);
/* Test 2: Test 2: Time taken to perform 10000000 validity checks on the fromJS Map is 1474.4121170043945ms, averaging 0.00014744121170043946ms. */
// Test 3: immutableJS Map
start = performance.now();
for (let i = 0; i < numTimes; i++) {
isValid(nestedPoint, '2-nested point');
}
end = performance.now();
console.log(
'Test 3: Time taken to perform ' +
numTimes +
' validity checks on the immutable Map is ' +
(end - start) +
'ms, averaging ' +
(end - start) / numTimes +
'ms.'
);
/* Test 3: Time taken to perform 10000000 validity checks on the immutable Map is 1248.7203179597855ms, averaging 0.00012487203179597855ms. */
Clojure
(ns benchmark (:require [clojure.spec.alpha :as s]))
(s/def ::x-coord int?)
(s/def ::y-coord int?)
(s/def ::point (s/keys :req-un [::x-coord]
:opt-un [::y-coord]))
(s/def ::nested-point (s/keys :req-un [::point]))
(s/def ::nested-nested-point (s/keys :req-un [::nested-point]))
(time (dotimes [_ 10000000] (s/valid? ::nested-nested-point {:nested-point {:point {:x-coord 2 :y-coord 3}}})))
(comment "Elapsed time: 31613.900138 msecs.")
As we may have expected, the immutable Maps take about the same times. We also note that the mutable version takes nearly three times as long as the immutable versions with this input.
For comparison purposes, clojure's spec/alpha
(which inspired this library) gives us 31613.900138 msecs, which is about 300 times our immutable version, and 30 times our mutable version implementation.
Suggested Usages:
perusal-immutable
, the APIs are able to specify the possible combinations of information it wishes to accept. Perusal-immutable can also be used to send your API specifications to your client, in the form of JavaScript files, so that your client can load the specifications and use them to check that the endpoints are forming valid API calls.Avoid when:
perusal-immutable
to verify the data.perusal-immutable
comes with performance costs since it has to check the type of the data.In general, perusal-immutable
is good for when we want to assert that the input data fulfills a certain structure before we perform further processing (e.g. sending it out to another API, data processing). With the immutable version, users do not have to worry about costs associated with repeated checking of data that is handled between functions, since the metadata will be stored if the same data is used.
Sure! Look at js.spec or speculaas.
Garett Tok Ern Liang (walnutdust)
This project is licenced under the MIT Licence.
Generated using TypeDoc


Exclusive Information Technology Cyber Security Bootcamp for Miramar-area High School Students
FVI School of Technology
3520 Enterprise Way
Miramar, FL 33025
The duration of the
program is 2 weeks
From July 30 - August 10
Monday thru Friday
from 9am to 1pm


Section A
This is the first section...
Section B
This is the second section...
Heading for paged media
Page:


Performs Gamma Correction on the input image.
tf.compat.v1.image.adjust_gamma
tf.compat.v2.image.adjust_gamma
tf.image.adjust_gamma( image, gamma=1, gain=1 )
Also known as Power Law Transform. This function converts the
input images at first to float representation, then transforms them
pixelwise according to the equation Out = gain * In**gamma
,
and then converts the back to the original data type.
image
: RGB image or images to adjust.gamma
: A scalar or tensor. Non negative real number.gain
: A scalar or tensor. The constant multiplier.A Tensor. A Gamma-adjusted tensor of the same shape and type as image
.
>> import tensorflow as tf >> x = tf.random.normal(shape=(256, 256, 3)) >> tf.image.adjust_gamma(x, 0.2)
ValueError
: If gamma is negative.For gamma greater than 1, the histogram will shift towards left and the output image will be darker than the input image. For gamma less than 1, the histogram will shift towards right and the output image will be brighter than the input image.
[1] http://en.wikipedia.org/wiki/Gamma_correction


WEEK 6 (01 March 2017)
[Electronics Design ]
This week the electronics design assignment is to redraw the Hello-World board and adding at least a Button and LED and check the design rules.
This week assignment is about learning how to design and fabricate a PCB from scratch using Eagle. The Art of Electronics is a great reference book for any component or Electrical circuit design.
And a good source for DataSheets of components is Octopart, we will need to visit the data sheet of certain components and learn how to connect it with certain values.
To make this task we were introduced to Eagle. This software let us make a layout with all the components. We can define path thickness and routes.
Getting Started With Eagle:
Step 1 - Download and install Eagle;
Step 2 - Sample echo board Schematic / board;
Step 3 - Download and install the components libraries;
Step 4 - Edit the schematic;
Steps followed:
First I downloaded the EAGLE 8.0.2 free version. (You can download eagle here, choose "free version of EAGLE")
This is the schematic echo hello-world board
After that we go to Fablab component library:
Copy the library into the install directory of eagle into a folder called "lbr" (in Windows it is most likely C:\Program Files\EAGLE\lbr\ (fact check this).
fab.lbr
I Created a new project:
File -> New -> Project
And I created a new Schematic and Board
I Activated the Component Libraries
I had a look at the Fab Inventory Spreadsheet which contains a list of all parts with codes and suppliers, and I checked it according to the datasheet of each component.
I Added a component in eagle: press "add" on the command line or press add in the tool bar. And search the components.
The components:
- 1X 6-pin programming header: for programming the board
Inventory: 649-95278-101A06LF
Fab library symbol: AVRISPSMD
- 1X Microcontroller: attiny44A. Once the microcontroller is programmed, the program stored in non-volatile memory. This means that it will remember the program.
Inventory: ATTINY44A-SSU-ND
Fab library symbol: ATTINY44 (We do not have ATTINY44 in Fab Lab because it's sold out, and so we'll use a ATTINY45)
- 1X FTDI header: powers the board and allows board to talk to computer
Inventory: CONN HEADER 36POS .100 R-A SMD (S1143E-36-ND)
Fab library symbol: FTDI-SMD-HEADER
- 1X 20MHz resonator: external clock. The attiny has a 8Mhz clock but the resonator is faster (increase the clock speed of the processor) and more accurate.
Inventory: CER RESONATOR 20.00MHZ SMD (XC1109CT-ND)
Fab library symbol: RESONATOR
- 2X Resistor (value 10k)
Inventory: RES 10.0K OHM 1-4W 1% 1206 SMD (311-10.0KFRCT-ND)
Fab library symbol: RES-US1206FAB
- 1X Button (OMRON switch)
Inventory: SW262CT-ND
Fab library symbol: 6MM_SWITCH6MM_SWITCH
- GND
- VCC
- 1X LED (Light Emitting Diode) - LEDs have polarity - the side with the line is the cathode and connects to the ground side.
Inventory: 160-1167-1-ND
Fab library: LEDFAB
- 1X Resistor (value 100 ohm)
Inventory: 311-100FRCT-ND
Fab library symbol: RES-US1206FAB
INTERFACE / BOARD
For switching to the board interface from the schematic I used the command line typing board pressing Generate/switch to board.
Making the schematic, commands (use the command line or the menu):
For moving a group of parts:
1_select move
2_select group
3_right click + command
I tried to make my board in full, but I had great difficulty making it so I decided to go the easy way, I downloaded the files of the board "Hello Echo", I opened the diagram and followed the steps to add the missing components, resistors, LED and button.
The components:
Resistor - A resistor is part of an electrical circuit that resists the flow of current.
Capacitor - A capacitor is a device used to store an electric charge, consisting of one or more pairs of conductors separated by an insulator. Capacitors are often used as filter devices to remove voltage or signal spikes in electronic circuits
Led - Light-emitting diode, a semiconductor diode that glows when a voltage is applied.
Vcc (Power) - Is positive relative to ground.
We will add components to the schematic view and create connections between them
The board layout shows how the electrical componets and traces will be laid out on the board.
After that I used the "Show" command in order to see the display of the components on the "Board", after that I was able to organise it the best way possible and I made the connections between the components using the "Route" tool, following the logic of the schematics.
EXPORTING THE DESIGN & MILLING
Once the design was finished and checked I exported PNG files of our design:
- Selected through LAYERS option the appropriate layers to export
- 500 dpi resolution
- MONOCHROME
- full area
- In Photoshop I edit the board
Settings should be MONOCHROME and 500 DPI - this will export an image with white traces, then "Export" as an image, afterwards I created a new layer based on the size of my board and painted it in "White" in photoshop.
Now it's time to generate the gcode. Using fabmodules website upload the .png files, select the process 1/64 for milling the traces and 1/32 to cut the outline. In Fablab Aldeias do Xisto we are using the Roland MDX 40-And the steps are the same of WEEK 4 [Electronics Production]:
- Open the image (PNG) in Fabmodules;
- I Selected the Machine ( Roland MDX 40) and the PCB traces 1/64;
- I change the Settings:
Cut depth - 0.1mm;
Tool diameter - 0.25mm;
Number of offsets - 3;
After that I "Process Calculate" ;
- Then I save de "rml file - boardfinal " and I opened it on the Vpanel of the Modela MDX40, where are the machine coordinate system anda I then changed the settings in X Y and Z ;
- Finally I delete de old file and opened my new "rml file", and then I output to start milling;
MILLING
Cut the Board
Final step
- Soldering;
- And the final Hello-World board with a Button and a LED;
Files:


Quality Crafted and Made to Last
Hand Crafted from kiln-dried hardwoods, this collection is upholstered in durable top-grain leather and mountain wildlife tapestry. Made to order in the USA from imported materials. Attached inside back cushions and reversible seat cushions. Available in custom sizes and designs.
Move your mouse over a section of the picture:


Favicon-Switcher v1.0
Favicon of this page reacts on OS UI mode switching and window resizing.
<800px
≥ 800px
Light
Dark


We will first look at Delaware and Washington, DC as examples, and then you will have a chance to look at your own location if it is different from these two.


WITNESS LIST Finance Committee February 10, 1997-9:30A SB 203 For: Box, Terry (Self), Plano On: Scott, Wayne (TDCJ), Huntsville Registering, but not testifying: On: McNutt, David (TDCJ), Huntsville Winters, Clint (Comptroller's Office), Austin SB 211 For: Bloom, Ed (TAEYC), Austin Rubin, Melanie (Child Care Group), Dallas Watson, Jeannette (TX Child Care Wkg Group), Austin On: Alexander Cindy (Comptroller's Office), Austin Martin, Charles (TWC), Austin Registering, but not testifying: For: Bresette, Patrick (CPPP), Austin Kamm, Robert (TAB/COC), Austin On: Coombs, Phyllis (Comptroller's Office), Austin Person, Leona (Comptroller's Office), Austin Written materials submitted: For: Engman, Nancy (Txns Care for Children), Austin SB 263 For: Green, Paul W. (4th Court of Appeals), San Antonio Registering, but not testifying: For: Hardberger, Phil (4th Court of Appeals), San Antonio SB 303 For: Bier, Samuel (CCC AM Ex-POWs), Austin


You have 10 new message.
The point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmThe point of using Lorem Ipsum is that it has a more-or-less normal.
Yesterday 2:45 pmYou have 20 projects. 5 not completed.
The point of using Lorem Ipsum is that it has a more or less normal.
1 hours agoCompletion with: 28%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
2 hours agoCompletion with: 68%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
3 hours agoCompletion with: 78%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
4 hours agoCompletion with: 38%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
5 hours agoCompletion with: 28%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
6 hours agoCompletion with: 68%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
7 hours agoCompletion with: 78%
Project end: 4:00 pm - 12.06.2014
The point of using Lorem Ipsum is that it has a more or less normal.
9 hours agoCompletion with: 38%
Project end: 4:00 pm - 12.06.2014
You have 20 Settings. 5 not completed.
Basic notifications Can be closed by clicking on it.
Notifications With image Can be closed by clicking on it.
Notifications Disable sound Can be closed by clicking on it.
Notifications Custom title Can be closed by clicking on it.
Notifications Without icon and image Can be closed by clicking on it.
Notifications Increase delay time Can be closed by clicking on it.
Notifications Sticky (without delay) Can be closed by clicking on it.
Notifications Alternative position Can be closed by clicking on it.
Notifications Custom Width Can be closed by clicking on it.
Can be closed by clicking on it. You can use any animate.css classes
Large Notifications Can be closed by clicking on it.
Mini notifications Can be closed by clicking on it.
Copyright © 2018 Colorlib All rights reserved. Template by Colorlib.


Boeing receives vote of confidence in 737 Max from Turkish airline Sun Express with $1.2bn order
by Alex DanielThe annual Dubai air show kicked off this week with billions of pounds-worth of aircraft deals, including a substantial order for 10 Boeing 737 Max jets which remain grounded worldwide after two fatal crashes.
Turkish airline Sun Express, which already has 32 of the planes on order, put its faith in the under-fire US manufacturer with an extra $1.2bn-worth of the jets.
Read more: ‘Series of failures’ caused Boeing’s 737 Max Lion Air crash
Chief executive Jens Bischoff said the firm “stands behind” its decision to phase the 737 Max into its fleet, and that it has “full confidence” in Boeing to make safe passenger jets.
It comes eight months after the second of two fatal crashes involving the model, which combined killed 346 people in Indonesia and Ethiopia.
The disasters have both been linked to an anti-stall system fitted in the plane, which forced the nose down to the ground despite the pilots’ best efforts.
Boeing has pledged to fix the issue, but has come under heavy criticism this year.
Read more: Europe ‘will not accept’ FAA’s safety decision on grounded Boeing 737 Max
“We are honored and humbled by the trust that Su nExpress has placed in our team at Boeing. They have been a wonderful partner over the years, demonstrating every day the efficiency and reliability of the Boeing 737 across their growing network,” said Stan Deal, president the company’s commercial airplanes unit.
“We regret the impact the Max grounding has had on Sun Express and their passengers. The Boeing team is working hard to safely return the airplane to service and providing the capacity for Sun Express to continue serving as the backbone of air travel in the Turkish tourism industry.”


Express checkout. Vacation Inn.
Charges for Room number: {{ entries[0].room }}
{% for entry in entries %}
{{ entry.item }}
{{entry.amount}} {% endfor %}


From the Semantic directory you can setup gulp to build Semantic by running.
npm install
Semantic will automatically configure itself using a post-install
script built into the package.
After set-up can use gulp to build your project’s css:
/* Watch files */
gulp watch
/* Build all files */
gulp build
Visit the Getting Started Guide for more details on set-up
Each gulp task can be imported into your own Gulpfile using require
var
watch = require('path/to/semantic/tasks/watch')
;
gulp.task('watch ui', 'Watch Semantic UI', watch));
LESS files do not contain vendor prefixes. If you are to use these files directly you must add them during your build step.
Before using source files you will need to create a theme.config
by renaming theme.config.example
, and a site folder by renaming _site/
to site/
You can then import Semantic from your own LESS files:
/* Import all components */
@import 'src/semantic';
To import individual components you will have to create a scope for each import using & {}
/* Import a specific component */
& { @import 'src/definitions/elements/button'; }
These files are generated automatically using install scripts, but must be manually renamed if you are using installing manually.
| filename | usage | Initial Name |
|---|---|---|
| theme.config | config file that stores each element’s current theme for LESS | theme.config.example |
| site/ | folder storing all your site’s variables and css overrides for each UI component | _site/ |
| semantic.json | stores folder paths for build tools and current installed version for updates. Only necessary when using build tools | semantic.json.example |
You will only need to use Semantic’s build tools while refining your UI. When designing pages, you can rely on the compiled css packages in dist/
.
When creating your UI you can try downloading different themes, adjusting your site-wide settings (font-family, colors, etc) and tweaking components in your site’s component overrides.
Files in the examples/
folder of your project can be useful for testing out changes in your UI. For example, you might run gulp watch
download a new theme to src/site/themes/
then adjust your theme.config
file with the name of the new theme and refresh examples/kitchensink.html
to inspect changes in the theme.
There are three levels of inheritance in Semantic
definitions/
contains the css
and javascript
definitions for each componentthemes/
contains pre-packaged themes including Semantic’s default themesite/
contains your current site’s themeView the Theming Guide for a more in-depth look
The best way to start customizing is to specify overriding variables in your site’s site.variables
file.
This is a blank stub file that lets you specify variables that overriding variables.
Some important values to customize:
To find out what variables are available to modify, you can inspect the variables in the default theme in themes/default/
Each component has its own variable file, which can be used to modify any of the underlying variables for that component.
For example /site/elements/button.variables
.
You may also specify your own custom LESS in site/elements/button.overrides
. This file will have access to all underlying variables available for that component.
You can modify theme.config
to use any prepackaged theme available in src/themes/
.
For example you can modify theme.config
to use a github
button theme by changing
@button: 'github';
View the Customization Guide to learn more


Home
Reservations
Temples
Services
Contact
☰
Reception
Reception Accomodations:
Reception hall
Ballroom
Kitchen for Catering
Catering options
Tables and Chairs
Other Services:
Rehersal dinner
Ring Ceremony services
Desserts/Wedding Cake services
Seamstress
Floral Services


Select Locations
{{selectTotal}} Selected
Select all
/
Deselect all
{{state.name}}
Select all
{{loc.address}}
{{loc.city}}, {{loc.state}}
{{loc.id}}
{{loc.name}}
There are no locations that match "{{searchQuery}}".
Please try again.


This page was created to calculate/log, retrieve, modify, and delete your personalized health data.


{% extends "base.html" %} {% block title %}Logged Out{% endblock %} {% block content %}
You have successfully logged out of Powermon.


cspice_georec cspice_latrec cspice_pxform cspice_pgrrec
cspice_radrec cspice_reccyl cspice_recgeo cspice_reclat
cspice_recpgr cspice_recrad cspice_recsph cspice_scdecd
cspice_scencd cspice_scs2e cspice_sphrec cspice_spkezr
cspice_spkpos cspice_str2et cspice_sxform cspice_timout
Top
Windows
Icy now includes interfaces to the full set of CSPICE window routines.
cspice_wnelmd cspice_wnincd cspice_wnreld cspice_wncomd
cspice_wncond cspice_wndifd cspice_wnexpd cspice_wnextd
cspice_wnfetd cspice_wnfild cspice_wnfltd cspice_wninsd
cspice_wnintd cspice_wnsumd cspice_wnunid cspice_wnvald
Top
Other new interfaces
The following new miscellaneous interfaces to SPICE routines were added
to Icy in this release:
cspice_bods2c cspice_card cspice_celli cspice_celld
cspice_dafopw cspice_dafrs cspice_deltet cspice_et2lst
cspice_pgrrec cspice_recpgr cspice_scard cspice_size
cspice_spkcov cspice_spkobj cspice_ssize
Top
Bug Fixes
Top
MKSPK Processing of TLE
A MKSPK bug causing the program to process improperly formatted TLE
files without signaling an error and producing output SPK containing bad
data was fixed.
Top
MKSPK Adding Comments When Appending to Existing SPK
A MKSPK bug causing the program, in some rare circumstances, to signal
an error when adding comments to an existing SPK file was fixed.
Top
A bug that caused the interface to fail to release allocated memory when
the FRAMEMISSING error signaled was fixed.
Top
A bug causing the DVPOOL routine to not delete a specified kernel pool
variable in some cases was fixed.
Top
CSPICE/kdata_c Function
A number of typos in the example provided in the header of the routine
were corrected.
Top
A bug causing the FRINFO routine to treat any frame with a negative ID
code and a frame definition not provided in the kernel pool as a
CK-based frame was fixed. Now, instead of returning ``manufactured''
attributes of a CK-based frame, the routine will generate an error for
such inputs.
Top
Version 57 --- March 2004
Top
Environments
The N0057 version of the SPICE Toolkit is supported on the same
environments as version N0056.
Top
Icy
The N0057 version offers the first official release of Icy, the
interface to the CSPICE library from Interactive Data Language (IDL), a
product of Research Systems, Inc. (RSI, http://www.rsi.com). If Icy was
provided with this package, refer to ``icy.req'' document and to the Icy
HTML documentation pointed to by ``doc/html/index.html'' for more
details.
Top
SPICELIB/CSPICE
Top
SRFXPT
This new routine computes the surface intercept point of a specified ray
on a target body at a specified epoch, optionally corrected for light
time and stellar aberration. Its purpose is the same as for the SPICE
routine SURFPT but unlike SURFPT is provides a much more flexible
interface and computes geometry adjusted for light time and stellar
aberration to the surface point rather than to the center of the target
body. Therefore for most cases this routine makes SURFPT obsolete.
Currently SRFXPT supports only the ellipsoid shape for target bodies but
in the future it may be extended to support digital terrain models.
Top
Support for Satellite IDs in the Range 10000-99999
NAIF PCK data access routines have been modified to recognize satellites
with IDs in the 10000-99999 range.
Top
Detection of Non-native Text Files
The SPICE data loading mechanism was extended to detect and prohibit
loading text kernel files containing lines terminated with EOF
character(s) non-native to the platform on which the Toolkit was
compiled. If a non-native EOL terminator is detected in the first 132
characters of a text kernel, the execution is stopped and an error
message is displayed. This feature does not work with files that are
smaller that 132 bytes or have the first line longer that 132
characters.
Top
Documentation
The Toolkit may now optionally include documentation in HTML format. It
is provided in the ``doc/html'' subdirectory and is pointed to by the
top level index file
doc/html/index.html
The headers of a few additional most often used routines have been
revised to correct technical errors and grammar and/or spelling, improve
clarity, and improve examples.
Top
Built-in NAIF ID Code/Name Definitions
The following new built-in NAIF ID code/name definitions have been added
to the Toolkit:
Spacecraft:
-79 SPITZER
Asteroids:
2000216 KLEOPATRA
Top
INSPEKT
INSPEKT was updated to generate comma-delimited reports. This output
format can be set using the ``SET FORMAT DELIMITED ...'' command. See
INSPEKT on-line help for more details.
Top
TOBIN
TOBIN was modified to detect and prohibit processing input transfer
files containing lines terminated with EOF character(s) non-native to
the platform on which the Toolkit was compiled.
Top
Version 56 --- August 2003
Top
Environments
The N0056 version of the SPICE Toolkit is supported on the same
environments as version N0055 except the following ``Classic'' Mac
environments:
Macintosh MacOS9 Absoft FORTRAN
Macintosh MacOS9 Metrowerks Codewarrior C
Contact NAIF if you wish to obtain the Toolkit for these two deprecated
environments.
Top
SPICELIB/CSPICE
Top
Documentation
The headers of 20+ of the most often used routines have been revised for
one or more of the following reasons:
-- to correct technical errors,
-- to add pertinent new information,
-- to correct grammar and/or spelling,
Top
Built-in NAIF ID Code/Name Definitions
The following new built-in NAIF ID code/name definitions have been added
to the Toolkit:
Spacecraft:
-74 MRO
-74 MARS RECON ORBITER
-130 MUSES-C
-142 TERRA
-154 AQUA
-159 EUROPA ORBITER
-172 SPACETECH-3 COMBINER
-188 MUSES-B
-190 SIM
-198 INTEGRAL
-205 SPACETECH-3 COLLECTOR
-234 STEREO AHEAD
-235 STEREO BEHIND
-253 OPPORTUNITY
-254 SPIRIT
Tracking Stations:
398990 NEW NORCIA
Jovian satellites:
528 AUTONOE
529 THYONE
530 HERMIPPE
531 AITNE
532 EURYDOME
533 EUANTHE
534 EUPORIE
535 ORTHOSIE
536 SPONDE
537 KALE
538 PASITHEE
Saturnian satellites:
619 YMIR
620 PAALIAQ
621 TARVOS
622 IJIRAQ
623 SUTTUNG
624 KIVIUQ
625 MUNDILFARI
626 ALBIORIX
627 SKADI
628 ERRIAPO
629 SIARNAQ
630 THRYM
Uranian satellites:
718 PROSPERO
719 SETEBOS
720 STEPHANO
721 TRINCULO
Top
CHRONOS
CHRONOS utility program has been modified to allow loading kernel files
using FURNSH kernel pool keywords and to accept all setup information
from the command line.
Top
Bug Fixes
Top
Reading Files with MAC-OSX Absoft FORTRAN Toolkit
Low level read routines were fixed to make sure that the OSX Absoft
FORTRAN SPICE toolkit can read files not owned by the user.
Top
DAS Scratch Files
DASCLS routine has been modified to call the routine flushing DAS
buffers before closing scratch DAS files. Failing to free the buffers
caused write errors on HP/FORTRAN systems.
Top
Argument Checking in CSPICE Error Handling Functions
The errprt_c, errdev_c, and erract_c functions were updated to diagnose
invalid operation keyword input.
Top
Version 55 --- March 2003
Top
Environments
The N0055 version of the SPICE Toolkit is supported on the same
environments as version N0054.
Top
SPICELIB
Top
SPKW01
SPK type 1 writer routine has been added.
Top
DASCLS
Scratch files no longer have their buffered portions flushed and are no
longer segregated before before being closed. This change speeds up the
close operation.
Top
SPKBSR
Segment buffer size was increased from 2000 to 10000 to improve
efficiency when handling SPK files with large number of segments.
Top
Kernel POOL
The buffer that stores distinct numeric data items from the text kernel
files was increased. The new buffer size is 20000, which is the maximum
total number of values for all numeric scalar and array pool variables
together.
Top
Type 1 SCLK
The buffer that stores Type 1 SCLK coefficients was increased. The new
buffer size is 10000.
Top
CSPICE
Top
New CSPICE wrappers
Wrappers dasac_c and dasec_c have been added to CSPICE. These support
DAS file comment area access.
Top
Bug Fixes
Top
Built-in NAIF ID Code/Name Definitions
The following built-in NAIF ID code/name definitions have been corrected
to match official MER name-ID mapping:
-253 was MER-A, now MER-1
-254 was MER-B, now MER-2
MER-A and MER-B names are no longer supported by the Toolkit.
Top
DASCUD
DASCUD has been fixed so that it writes a new, empty cluster directory
record at the correct location. This corrects an error introduced by a
bug fix in N0054.
Top
OSCELT
OSCELT has been fixed so that it computes the argument of periapse
correctly when the inclination is zero or 180 degrees. The mean anomaly
computation has been corrected so that it works for circular and
near-circular orbits. The computation of inclination has been changed to
use ATAN2 for improved accuracy. Code that could generate arithmetic
exceptions was corrected. Several new error checks have been added.
Top
CKE05
Angular velocity computations for subtypes 0 and 1 have been changed to
make them compatible with those used by the MEX/Rosetta attitude file
interpolation algorithms.
Top
CKBRIEF
CKBRIEF has been updated to retrieve and display interpolation interval
information from Type 2 CK files correctly in all cases.
Top
Version 54 --- December 2002
Top
Mailing Lists
NAIF has created 2 mailing lists, ``Spice_announce''
http://naif.jpl.nasa.gov/mailman/listinfo/spice_announce
and ``Spice_discussion''
http://naif.jpl.nasa.gov/mailman/listinfo/spice_discussion
``Spice_announce'' is intended to provide notification of important
developments such as a new toolkit release. Posting will generally be
limited to members of the NAIF team. If you feel you have an important
announcement that would be suitable for this list, you may send email to
the list, but it will be reviewed by the NAIF team before dissemination.
``Spice_discussion'' is meant to provide a forum for discussion among
SPICE users. Posting on this list is encouraged, however we also
encourage you to limit mail traffic to the entire list. Extended
discussions are often best carried out with a limited distribution list.
Both lists require registration, allow access to an archive of prior
postings and allow the user to choose whether to receive individual
postings or a daily digest.
Top
Environments
The N0054 version of the SPICE Toolkit is supported on the same
environments as version N0053.
Top
COOKBOOK Programs
FORTRAN and C versions of the COOKBOOK programs have been made more
consistent in implementation and behavior. User's Guide documents for
COOKBOOK programs have been updated and are now delivered with both
FORTRAN and C toolkits. The FSTSPK COOKBOOK program has been deprecated
and is no longer delivered.
Top
New Built-in NAIF ID Code/Name Definitions
The following new built-in NAIF ID code/name definitions have been added
to the toolkit:
Spacecraft:
-226 ROSETTA
Jovian satellites:
517 CALLIRRHOE
518 THEMISTO
519 MAGACLITE
520 TAYGETE
521 CHALDENE
522 HARPALYKE
523 KALYKE
524 IOCASTE
525 ERINOME
526 ISONOE
527 PRAXIDIKE
Top
Documentation
User's Guide documents for TOBIN, TOXFR and VERSION utility programs
have been added to the toolkit documentation.
Top
Bug Fixes
Top
Built-in Body-Fixed Frame for Pan
Definition of the built-in body-fixed frame for PAN (IAU_PAN) has been
updated to point to the correct PCK values used to compute its rotation.
In the previous version of the toolkit it was pointing to PANDORA's
rotation constants.
Top
Surface Intercept Routine
The surface intercept routine SURFPT/surfpt_c has been re-implemented to
reduce loss of precision.
Top
DAS Writer Routines
DAS utility routine DASCUD has been fixed to ensure that DAS file
structure is correct when files are closed without data segregation.
Previously it was possible for unsegregated files to have an invalid
final forward directory pointer. Note: this problem could not occur in
E-kernels created by SPICE utility programs or using the SPICE EK API
routines.
Top
CSPICE Cell Implementation
The CELLINIT macro has been updated so that it doesn't modify data added
to character cells prior to cell initialization. This enables population
of uninitialized character cells via macro calls.
Top
Body Name to Associated Frame Conversion Routine
The routine CNMFRM retrieving the reference frame name for a specified
body name has been fixed so a TK frame specified by name and designated
as an object's preferred frame via kernel pool assignments is found, and
so that the correct name of this frame is returned.
Top
CHRONOS
CHRONOS has been updated to make sure that the iterative search for the
nearest local midnight converges in all cases. It has also been updated
to use the maximum system allowed file name length on VAX and DEC Alpha
environments.
Top
Version 53 --- September 2002
Top
Environments
The N0053 version of the SPICE Toolkit is supported in the following
environments:
PC Linux g77
PC Windows Compaq Visual (Digital) FORTRAN
PC Windows Lahey FORTRAN 95
PC Linux gCC
PC Windows Microsoft Visual C++
Sun Solaris FORTRAN
Sun Solaris Native C
Sun Solaris gCC
HP UX HP FORTRAN
HP UX HP C
Macintosh MacOS Absoft FORTRAN
Macintosh MacOS Metrowerks Codewarrior C
Macintosh OS-X g77
Macintosh OS-X Absoft FORTRAN
Macintosh OS-X Apple C
SGI IRIX N32/O32 FORTRAN
SGI IRIX MIPS C (N32/O32 ABIs)
DEC Alpha Digital Unix Digital FORTRAN
DEC Alpha Digital Unix Digital C
Vax VMS Digital FORTRAN
The PC/Linux/g77 version previously supported the alternative ``fort77''
compiler. This is no longer the case. Contact NAIF if you need support
for this compiler.
The Macintosh OS-X environments are new.
Top
CSPICE
Top
New CSPICE wrappers for cell, set, and windows routines
The complete set of C wrappers duplicating cell, sets, and windows
capabilities existing in FORTRAN SPICE has been added to CSPICE.
Top
New CSPICE wrappers for sorting and searching routines
The following new CSPICE wrappers implementing sorting and searching
capabilities have been added:
bscho*_c.c
bsrch*_c.c
esrchc_c.c
isordv_c.c
isrch*_c.c
lstle*_c.c
lstlt*_c.c
order*_c.c
reord*_c.c
shell*_c.c
Top
New CSPICE wrappers for string manipulation and parsing routines
The following new CSPICE wrappers for string manipulation and parsing
capabilities have been added:
cpos*_c.c
pos*_c.c
ncpos*_c.c
kxtrct_c.c
lpars*_c.c
lx4*_c.c
lxqstr_c.c
repm*_c.c
Top
SPICELIB
Top
SPK Type 18
A new SPK type (Type 18) has been added. This incorporates ESA/ESOC
model for a spacecraft ephemeris.
Top
CK Type 5
A new CK type (Type 5) has been added. This incorporates ESA/ESOC model
for a spacecraft attitude data.
Top
BRIEF
BRIEF utility has been updated to allow summarizing SPKs containing
ephemerides for up to 20,000 distinct bodies.
Top
COOKBOOK
COOKBOOK programs have been updated to use the highest level routines
currently available in SPICE -- FURNSH, SUBPT, etc.
Top
Bug Fixes
Top
ID-to-name Translation
SPICE's ID-to-name mapping subsystem has been updated to provide
consistent behavior across all of its interfaces. It now correctly
processes duplicate ID-to-name mapping assignments provided via text
kernel files. Refer to the NAIF_IDS Required Reading for more details.
Top
Built-in Body-Fixed Frames
Missing body-fixed frames -- IAU_PAN, IAU_GASPRA, IAU_IDA, and IAU_EROS
-- have been added to the built-in frame set.
Top
Binary architecture consistency check at run-time
Binary file format consistency check has been implemented at run time to
verify that the toolkit prepared specifically for a platform with one
binary file format has not been compiled/used on a platform with another
binary file format.
Top
Long/truncated lines in text kernel files
The text kernel file reader has been modified to correctly process
truncated string value assignments.
Top
VMS Read-Only Access File Open Failure
A bug in the DAF system preventing users on VMS systems from loading
SPK, CK and binary PCK files with the read-only attribute(*) has been
fixed.
Top
Version 52 --- January 2002
Top
Environments
The N0052 version of the SPICE Toolkit is supported on the following
environments:
PC Linux G77
PC Windows Compaq Visual (Digital) Fortran
PC Windows Lahey Fortran 95
PC Linux GCC
PC Windows Microsoft Visual C++
Sun Solaris Fortran
Sun Solaris Native C
Sun Solaris GCC
HP UX HP Fortran
HP UX HP C
Macintosh MacOS Absoft Fortran
Macintosh MacOS Metrowerks Codewarrior C
SGI IRIX N32/O32 Fortran
SGI IRIX MIPS C (N32/O32 ABIs)
DEC Alpha Digital Unix Digital Fortran
DEC Alpha Digital Unix Digital C
Vax VMS Digital Fortran
The N0052 version of the SPICE Toolkit is no longer supported on the
following environments:
PC Windows Lahey F77L3
PC Windows Microsoft Powerstation Fortran 1.x
PC Windows Microsoft Powerstation Fortran 4.x
Sun SunOS Fortran
Macintosh MacOS Language Systems Fortran
Next Nextstep Absoft Fortran
Next Nextstep GCC
Contact NAIF if you wish to obtain the Toolkit for one or more of these
deprecated environments.
Top
SPICELIB
Top
Run-Time Binary File Format Translation
The most popular supported systems (including Macintosh, PC, and UNIX
platforms) are now capable of accessing data in binary SPICE kernel
files from other platforms directly without using transfer format. But
note that binary files from other platforms are only available for read
access. See the Convert User's Guide for specifics and details.
Top
Open File Limit Increase
The sum of loaded SPK, CK, and binary PCK files, all of which are
implemented using the DAF file architecture, may now reach 1000.
Previous versions of the toolkit restricted the number of loaded DAFs to
20. But caution: loading large numbers of files may impact system
performance.
Top
SPK aberration corrections
SPK readers can now perform aberration corrections for transmitted, as
well as received, radiation. This feature makes it simple to compute the
direction in which radiation must be emitted in order to reach a
specified target.
The headers of the SPK readers have been expanded to explain aberration
corrections in greater detail.
Top
Instrument Kernel Support
GETFOV was extended to compute boundary corners from FOV definitions in
the kernel pool utilizing the new ANGLES specification. See GETFOV's or
getfov_c's header for details.
Top
Kernel POOL
The buffers that store text kernel data were increased. The new maximums
are:
Maximum Number of Variables 5003
Maximum Number of Distinct Numeric Data Items 10000 (*)
Maximum Number of Character Strings 4000 (**)
(*) This is the maximum total number of values for all numeric scalar
and array pool variables together. (**) This is the maximum total number
of values for all character scalar and array pool variables together.
These changes allow the kernel pool to hold substantially more data than
previous versions of the SPICE toolkit, which became necessary due to
the increasing use of such SPICE components as IK and FK utilizing the
POOL as the data repository and access mechanism.
Top
Jacobian routines
Routines have been added for computing the Jacobians of the
transformations between rectangular and the following coordinate
systems:
cylindrical
geodetic
latitudinal
spherical
The Jacobian routines support transformation of velocities between these
coordinate systems. See the headers of the following SPICELIB
routines/CSPICE functions for more information:
DCYLDR/dcyldr_c
DGEODR/dgeodr_c
DLATDR/dlatdr_c
DSPHDR/dsphdr_c
DRDCYL/drdcyl_c
DRDGEO/drdgeo_c
DRDLAT/drdlat_c
DRDSPH/drdsph_c
Top
NAIF ID to Object Name Mapping
The NAIF IDs for the following missions has been added to the set of IDs
built into SPICE:
CONTOUR
LUNAR-A
DRTS-WC
MARS EXPRESS
DEEP IMPACT
STARLIGHT
MER
Top
Documentation
DAS and EK Required Reading documents have been added to the SPICE
Toolkit.
The CONVERT User's Guide has been updated to reflect new run-time binary
file format translation capability.
The FRAMES Required Reading has been updated to include inertial frame
information formerly contained in the NAIF_IDS Required Reading.
The NAIF_IDS Required Reading has been updated to reflect new Toolkit
capability, through which the NAIF ID to name mappings can be defined
using text kernel files.
The MKSPK User's Guide has been updated to add clarity throughout.
The ERROR, PCK, ROTATIONS, SPK, and TIME Required Reading documents have
all been improved.
Top
CSPICE
Top
New CSPICE wrappers for EK routines
CSPICE wrappers have been added to support record-oriented EK
manipulation, including record-oriented writing, updating, and reading.
CSPICE wrappers have been added to provide summary capabilities for
loaded EK tables.
Top
Miscellaneous new CSPICE wrappers
Some new CSPICE wrappers have been added:
frmnam_c
inelpl_c
namfrm_c
Top
CKBRIEF
A capability to display a separate record for each interpolation
interval in each segment of a Type 2 or Type 3 CK file has been added to
the program. This capability is implemented using the ``-dump'' command
line option.
Top
COMMNT
An inconsistency between the program's functionality in interactive and
command line modes has been fixed. The maximum length of a comment line
that can be added to and extracted from the comments in either mode is
now the same and is equal to 1000 characters.
Top
MKSPK
The program was modified to allow appending new data segments to an
existing SPK file.
Top
VERSION
The interface of this utility program has been extended: a command line
parameter causing the program to display additional library information
has been added. See ``version -help'' for details.
Top
Bug Fixes
Top
CK, PCK, and SPK segment buffering and selection
Several bugs have been corrected in the modules CKBSR, PCKBSR, and
SPKBSR. These bug fixes enable users to load more segments than can be
buffered at once by these modules. However, the best run-time speed is
still obtained when all segments of a given kernel type can be buffered.
The current segment buffer sizes are:
CK: 4000 segments
SPK: 2000 segments
PCK: 100 segments
Top
Const-qualification for various CSPICE interfaces
A number of CSPICE function interfaces have been updated to add
const-qualification of input arrays. This fix enhances compatibility
with C++ applications.
Top
CSPICE function gcpool_c fixed
This routine did not properly trim trailing blanks from values in its
output array.
Top
MOVED fix for Fortran PC Linux platform
In some cases the routine MOVED incorrectly copied double precision
numbers whose values were assigned via EQUIVALENCE statements with pairs
of integers. This could happen when the integer bit patterns did not
correspond to valid double precision numbers. This problem prevented
correct manipulation of some DAF segment descriptors.
Top
EK query processing using LIKE operator and null values
Null values could be returned in some rare circumstances when a query
employed the LIKE operator to compare scalar string column entries
against a specified string value, and a null column entry was compared.
Top
EK time conversion
The EK time parsing code handled SCLK values incorrectly when the string
``SCLK'' appeared in the name of the clock.
Top
EK documentation
Various headers have been updated to indicate that query-and-fetch
operations and EK fast writer operations may not be interleaved.
Top
Source code clean-up
Miscellaneous problems triggering annoying but insignificant compilation
warnings have been fixed. Various files have had TAB characters removed.
Others have had final newline characters added.
Top
Version 51 --- April 2000
Top
SPICELIB
Top
Instrument Kernel Support
The routine GETFOV was added to the Toolkit. It returns information
describing the shape, size, boresight, and orientation of the field of
view for traditional remote sensing instruments.
Top
Binary Kernel Recognition
The routine GETFAT was upgraded to use a more robust algorithm for
identifying the type (SPK or CK) of inadequately labeled binary kernels.
This modification is critical for Mars project SPICE customers who wish
to use the SPICELIB utility FURNSH when loading binary kernels.
Top
CK
A new representation for the orientation of spacecraft structures has
been added to the C-kernel system. C-kernel data type 04 provides a
flexible and compact method for representing the attitude of structures
by using Chebyshev polynomials to fit orientation data or models.
Top
SPK
Two new representations for position and velocity of objects have been
added to the SPK system. Types 12 and 13 provide for the Hermite
interpolation of states from series of state vectors. See the SPK
Required Reading for further details.
Top
Miscellaneous
The list of names recognized by BODTRN was enhanced to support the
identification of the "Cluster" spacecraft (1,2,3 and 4) as well as the
Pluto-Kuiper Express spacecraft and simulation.
Top
MKSPK
The utility program MKSPK has been added to the general release of the
SPICE Toolkit. This allows SPICE customers to more easily generate SPK
files from tabular ephemeris information. See the User's Guide
(mkspk.ug) for details on the use of MKSPK.
Top
SPKMERGE
The program was upgraded to correct an "infinite loop" that existed in
rare cases on some platforms.
Top
Bug Fixes
Although it is unlikely that most users will notice any difference, a
number of minor bug corrections have been incorporated:
-- The kernel pool software was modified to detect and handle string
specifications that are too long to be stored in the kernel pool.
-- The time parsing software (used by STR2ET) was enhanced so that erroneous
long strings will be diagnosed as erroneous and no longer cause a run-time
error.
Top
Version 50 --- October 1999
Top
CSPICE
Version 50 of the SPICE Toolkit includes a C language edition of the
Toolkit. This provides a C language interface to the Toolkit and
duplicates the FORTRAN capabilities. SPICE users interested in a C
version of the Toolkit should specifically request the CSPICE version.
Moreover, C users should read the document "CSPICE User's Guide" which
addresses issues regarding the translation of the FORTRAN Toolkit to C.
Top
Additions and Extensions to SPICE routines
Top
Loading Kernels
The new routine FURNSH provides a single uniform interface for loading
all SPICE kernels. In addition, the new interface allows you create a
"meta-kernel" listing which SPICE kernels should be loaded. When this
"meta-kernel" is supplied to FURNSH, all listed kernels will be loaded
into the appropriate SPICE subsystems. It is anticipated that this new
interface will substantially ease the problem of managing and loading
SPICE kernels.
In addition to the routine FURNSH several related routines are provided
to assist with the run-time management of kernels loaded through the
FURNSH interface.
-
KTOTAL
-
returns the number of kernels that are currently available to your
program as a result of previous calls to FURNSH and UNLOAD.
-
KDATA
-
provides an interface for retrieving (in order of their specification
through FURNSH) kernels that are active in your application.
-
KINFO
-
allows you to retrieve information about a loaded kernel using the name
of that kernel.
-
UNLOAD
-
provides an interface for unloading kernels that have been loaded via
the routine FURNSH.
FORTRAN users should consult the header for the routine KEEPER for
details on the use of these routines. C users should see the specific
files furnsh_c.c, ktotal_c.c, kdata_c.c, kinfo_c.c and unload_c.c
Top
Position Only Interface.
The Frames and SPK subsystems have been extended to provide a "position
only" interface. The user level routines in the extension are:
-
SPKPOS
-
returns the 3-vector giving the location of one object as seen from
another corrected for light time and stellar aberration (if requested
by the user) in the user specified reference frame.
-
PXFORM
-
returns the 3x3 matrix that transforms positions from one reference
frame to another as a function of time.
These routines run slightly faster than their position and velocity
counter parts: SPKEZR and SXFORM. In addition they allow you to use
C-kernel based frames when the C-kernel does not contain angular
velocity data.
See the routines PXFORM and SPKPOS for details on their use.
Top
ID-codes
The name/ID-code translation routines (BODN2C and BODC2N) have been
extended so that users may add missing name/ID-code mappings to SPICE
text kernels. Using this new capability, users can extend the built-in
name/ID-code mapping by simply loading an appropriate SPICE text kernel
with the interface FURNSH.
Top
Kernel Pool Enhancements
Several new kernel pool interfaces have been provided
-
STPOOL
-
Allows storage of long string valued variables through use of a
continuation character.
-
PCPOOL
-
Allows the insertion of a character variable directly into the kernel
pool without supplying a text kernel.
-
PDPOOL
-
Allows the insertion of a double precision variable directly into the
kernel pool without supplying a text kernel.
-
PIPOOL
-
Allows the insertion of an integer variable directly into the kernel
pool without supplying a text kernel.
-
LMPOOL
-
Similar to LDPOOL, but the text kernel is stored in an array of strings
instead of an external file.
-
SZPOOL
-
allows run time retrieval of kernel pool memory parameters.
-
DVPOOL
-
allows deletion of a specific variable from the kernel pool.
-
GNPOOL
-
assists in determining which variables are defined in the kernel pool
via variable name template matching.
Top
Continuous Spacecraft Clocks
The Spacecraft Clock system has been extended so that "ticks" can be
modeled continuously instead of discretely. See the SCLK required
reading for more details.
Top
Bad FTP File Transfer Detection
SPICE binary kernels have been enhanced so that Toolkit software can
detect whether a binary kernel has been transferred using ASCII instead
of BINARY transfer mode. Note that only SPICE binary kernels produced
with the N0050 (or later) version of the SPICE Toolkit will have
features required for this diagnosis.
Top
CK Writer Enhancements
The SPICE C-kernel writers have been enhanced to check that quaternions
supplied to the writer are indeed nearly unit length. This check allows
detection of programming errors earlier in the kernel production
process.
Top
Bugs
No bugs were identified between version N0049 and N0050 of the Toolkit.
However, users may notice that several routines have minor changes. The
main reasons for code changes are:
1. Extending the range of inputs that can be handled by SPICE routines.
2. Balancing the use of the SPICE error handling Check-in/Check-out tracing
mechanism.
3. Removal of unused variables.
4. Corrections in grammar, spelling and other typographic errors in the
headers of SPICE routines.
Top
SPICE Utility Programs
Top
TOBIN
The utility program TOBIN which converts transfer format kernels to
binary form, can now process transfer format kernels that have been
wrapped with SFDUs.
Top
COMMNT
COMMNT now accepts command line arguments making it usable from user
scripts.
Top
CKBRIEF
CKBRIEF is a new utility that allows you to quickly summarize a C-kernel
in a manner similar to the summary capabilities provided by the SPK
summary tool, BRIEF.
Top
MKSPK
MKSPK is a utility program that allows users to generate SPK files from
appropriate and suitably tabularized position and velocity information.
Top
Documentation
Many SPICE documents were edited and brought up to date. Most notable of
these is the document KERNEL.REQ which discusses SPICE text kernels and
the use of the kernel pool.
In addition a new document called "Common Problems" (problems.req) has
been included with the standard SPICE documentation. This document is
intended to help you in trouble shooting problems that may arise with
programming with the SPICE Toolkit.
Top
Version 49 --- September 1998
Version 49 of the SPICE Toolkit exists only to fix errors that were
identified in version 48 of the Toolkit. The routines in SPICELIB that
were corrected are:
DELTET --- obsolete routine maintained only for
backwards compatibility. A bug was
introduced in Version 48 that could
lead to 0.003 seconds of error in outputs.
DPFMT --- documentation corrections.
EKQMRT --- a boundary bug was corrected.
SPKW02 --- documentation correction
TIMDEF --- a bug was fixed that can only be manifested
when the default exception handling is modified.
TIMOUT --- correction of grammatical errors in header.
Top
Version 48 --- May 1998
Version 48 of the SPICE Toolkit extends the set of supported platforms
to include PCs running the LINUX operating system.
The time system was modified so that two digit years are interpreted as
belonging to the years 1969-2068 inclusive.
In addition a number of minor bugs have been fixed. The intended
functionality of the Toolkit has not changed. The most significant bug
fixes are listed here.
conics.for was updated.
There was a coding error in the computation of the mean
anomaly in the parabolic case. This problem has been
corrected.
et2lst.for was updated.
The integer variable SUN was never initialized in the
previous version of the routine. Now it is set to
the proper value of 10.
str2et.for was updated.
The previous versions of this routine did not correctly
convert day-of-year strings in the TDB or TDT systems.
They treated the day of year as year, month, day giving
spectacularly wrong answers.
In addition, comments concerning the default century for
abbreviated years were updated to reflect changes to TEXPYR
timout.for was updated.
The previous version of this routine did not output
fractional components for epochs prior to 1 A.D.
In addition, the default time system, calendar and time zone
are obtained from TIMDEF.
Top
Version 47 --- July 1997
This chapter describes the significant changes to version 47 of the
SPICE Toolkit.
Top
Documentation
There are two significant documentation changes to version 47 of the
Toolkit.
1. The Required Reading for SPK (SPK.REQ) has been re-written to address the
use of non-inertial frames within the SPK system.
2. The Frames subsystem has been documented in the required reading file
FRAMES.REQ. This document describes the various reference systems that are
currently supported by the Toolkit as well as naming and numbering
conventions that will be adhered to by NAIF.
These two documents together with the extensions to the frame system
that have been added in version 47 allows one to easily model the
dynamics of structures on spacecraft or surface rovers.
In addition to these major modifications to the base SPICE
documentation, the document TIME.REQ has been updated to reflect a
slight broadening of recognized time strings and to document the routine
ET2LST that allows the user to convert to ephemeris time to local solar
time for any natural ephemeris object.
Top
Software
Top
SPK
The SPK ephemeris system has been expanded to support Space Command Two
Line Elements (formally known as NORAD Two Line Elements) and
equinoctial elements.
To assist SPICE users who need to create SPK files that contain two line
element sets, NAIF has a preliminary utility that allows the creation of
SPK files from two line element data. This tool is available from NAIF
on an as-needed basis. This utility is still a bit rough around the
edges and has not yet been made an official Toolkit product.
Top
Frames
The frame system has been extended to support reference frames that can
be described as a constant rotation from another frame (such as a
bodyfixed, inertial or C-kernel frame). These frames are easily
described using text based kernels. This new frame type is well suited
for describing instrument, lander and topocentric frames.
Top
Time
The time parsing software was enhanced so that a slightly broader set of
time formats are recognized. In addition the routine ET2LST was added to
the Toolkit. This routine allows you to convert ET (ephemeris time TDB)
to local solar time for a planet, satellite comet or asteroid. Local
solar time is a "clock" measure of the angle between a local meridian
and the meridian of the sun. See the TIME required reading for further
details.
Top
Bug Fixes
The routines CKGPAV and CKFXFM in versions prior to version 47 of the
Toolkit dealt with angular velocity in non-inertial frames incorrectly.
This error did not affect C-kernels that were described relative to
inertial frames. In those rare instances in which a C-kernel was
described relative to a non-inertial frame, the mistreatment of angular
velocity could lead to errors in the computation of velocities relative
to the C-kernel frame. The computation of positions were not affected by
this error.
The routine TIMOUT in version 46 did not reliably produce an abbreviated
two-digit year. This error has been corrected.
All other errors were of a technical nature such as improper use of the
SPICE exception handling subsystem and are unlikely to have affected
most SPICE users.
Top
Version 46 --- January 1997
This chapter describes the significant changes to version 46 of the
SPICE Toolkit.
Top
Documentation
NAIF now has available two overview documents that provide users with a
higher level view of Toolkit. The two documents are called
Introduction to SPICE
Most Useful SPICELIB Subroutines
These documents are available in the ``doc'' subdirectory of the Toolkit
in the postscript files
intro.ps
mostused.ps
respectively.
The first of these documents, ``Introduction to SPICE'', provides a
broad overview of the SPICE system and attempts to lay out a map of
where you can find more specific information about the various
components of the SPICE system. The second document ``Most Useful
SPICELIB Routines'' categorizes 120 or so of the most frequently used
SPICELIB routines and provides a synopsis for each of these.
Top
Time
The time software has undergone significant enhancement. The Toolkit now
supports a wider set of time formats and time systems. The most
important new routines are:
STR2ET
TIMOUT
TTRANS
TPARTV
The new time software is outlined in the ``recommended reading'' file
--- TIME.REQ which appears in the ``doc'' subdirectory of the Toolkit.
A number of convenience routines have been added to the Toolkit. Those
likely to be of most interest to users are:
-
DPFMT
-
The routine DPFMT allows you to create a string representing a number
by supplying a ``picture'' that should be followed in formatting the
string.
-
TOSTDO
-
The routine TOSTDO is a portable means of writing strings to ``standard
output.'' The particulars of formatting on various platforms are
handled transparently. Using this routine, you can isolate yourself
from formatting considerations that arise when using the intrinsic
FORTRAN WRITE statement.
The remainder of the modifications to the Toolkit are primarily to ease
problems associated with maintenance of the Toolkit.
Top
Version 45 --- October 1996
Version 45 is a quick update to correct an oversight in versions 43 and
44. Although the reference frames DE-143 was added to the collection of
non-inertial reference frames in version 43, it was not available to all
of the SPICE subsystems. Version 45 corrects this deficiency.
In addition to this correction to the reference frame subsystem, a
number of minor corrections were made to the DAS subsystem and to error
messages returned by EK software.
Top
Version 44 --- August 1996
This chapter describes the significant changes to version 44 of the
SPICE Toolkit.
Top
SPK Subsystem
The main workhorse routine of the SPK subsystem, SPKGEO, was modified to
remove potentially redundant computations. As a result, some
applications may see a performance improvement on the order of 60
percent.
Top
Inspekt
Inspekt was upgraded to support the DEC Alpha OSF/1 environment. All
functional aspects of Inspekt are now fully supported in the DEC Alpha
OSF/1 environment.
Top
Bug Fixes
Several errors in the EK and supporting DAS subsystem were corrected.
These fixes will be visible to only a small number of SPICE users.
(Primarily those users who create E-kernels or access the EK files
directly through the subroutine interface.) Users whose primary use of
E-kernels is via the program Inspekt will see no visible changes in the
SPICE system.
The generic segment subsystem was corrected. The errors were discovered
by the NAIF staff while developing new SPK data types. These new data
types are not yet incorporated into SPICELIB. Consequently users of the
SPICE system are unlikely to have used any of the code in which these
errors were found.
The frames subsystem was corrected. In NAIF's experiments in converting
the library to C, an error was found in the routine FRMCHG. This error
is of a pedantic nature and has not surfaced in any of the supported
native FORTRAN environments.
Top
Version 43 --- May 1996
This chapter describes the new capabilities available in version 43 of
the SPICE Toolkit.
Top
Brief
The SPICE utility program BRIEF has been added to the generic SPICE
Toolkit. This program allows you to easily summarize the contents of an
SPK file. The summary can be tuned depending upon the level of detail
you are interested in seeing. See the BRIEF User's Guide (brief.ug) for
an explanation of features.
Top
Star Catalogs.
In version 43 of the SPICE Toolkit, an introductory level star catalog
capability has been introduced. The routines used for manipulating star
catalogs are:
STCF01
STCG01
STCL01
Top
CHGIRF
Support for the inertial reference frame DE143 has been added to
SPICELIB.
Top
BODTRN
The routine BODTRN has been added to the Toolkit. This routine allows
you to easily translate between the names of ephemeris objects to their
NAIF ID codes.
Top
Performance Improvements
A number of performance enhancements have been included. Most notable in
this list is the SPICE exception handling subsystem. By relinking your
programs you may see an improvement in performance from 20 to 30 percent
(depending upon how heavily your program makes use of the SPICE
exception handling capability).
Top
Version 42 --- December 1995
This chapter describes new capabilities available in version 42 of the
SPICE Toolkit and includes examples of how to make use of these new
capabilities. The major new capability of Version 42 of the Toolkit is
the official release of the SPICE Events Kernel Software. This software
includes all the interface level routines for reading and writing events
kernels. It also includes the event kernel browser program Inspekt.
Inspekt has an extensive on-line help facility that for now must serve
as a user's guide to the program.
Full documentation for the new capabilities will be available in version
43 of the Toolkit.
Top
Version 41 --- October 1995
This chapter describes new capabilities available in version 41 of the
SPICE Toolkit and includes examples of how to make use of these new
capabilities. There are two major new capabilities provided in version
41 of the Toolkit. First is the ability to retrieve the states of
objects by using the names of the objects instead of SPICE integer
id-codes for those objects. Second is the ability to store and retrieve
states of objects relative to non-inertial reference frames.
Until now, the primary mechanism for retrieving state information from
the SPICE ephemeris (SPK) files has been the subroutine SPKEZ
(pronounced: ess pee kay eee' zee). This routine requires that you know
the integer id-codes associated with the objects of interest.
Beginning with version 41 of the SPICE Toolkit the routine SPKEZR
(pronounced: ess pee kay eee' zee er ) will be the primary mechanism for
retrieving states. The calling sequence for this new routine is
CALL SPKEZR ( TARG, ET, REF, ABCORR, OBS, STARG, LT )
where
Inputs:
-
TARG
-
is a character string that is the name of the object whose state is of
interest. Examples are: 'JUPITER', 'EARTH', 'SUN', 'GOLDSTONE'.
-
ET
-
is the epoch at which the state is desired. ET is a double precision
number giving the epoch measure in ephemeris seconds past the epoch of
the J2000 reference frame.
-
REF
-
is a character string giving the name of the reference frame in which
the output state should be represented. Examples are: 'J2000',
'IAU_EARTH'.
-
ABCORR
-
is a string indicating what forms of aberration corrections should be
applied to the retrieved state.
-
OBS
-
is a string that is the name of the object to which the returned state
will be relative. Examples are: 'EARTH', 'GOLSTONE'.
Outputs:
-
STARG
-
is the state of the target body relative to the observer represented in
the specified reference frame with the specified aberration corrections
accounted for.
-
LT
-
is the light time in seconds from the target to the observer.
To illustrate the use of this routine, suppose that you wanted to get
the B1950 state of Mars relative to Earth corrected for light-time and
stellar aberration at the epoch that occurs 10 million seconds prior to
the J2000 epoch. The code fragment below shows how you would call SPKEZR
to obtain this state. (Note that this assumes that you have already
loaded ephemerides for Mars and the Earth.)
DOUBLE PRECISION STATE ( 6 )
DOUBLE PRECISION LT
CALL SPKEZR ( 'MARS', 1.0D+07, 'B1950', 'LT+S',
. 'EARTH', STATE, LT )
Top
Non-inertial Reference Frames
Prior to version 41 of the Toolkit, storing or obtaining states relative
to a body-fixed frame required conversion to or from states relative to
inertial frames such as J2000. With version 41 of the SPICE Toolkit,
this restriction has been removed. It is now possible to store states
relative to a non-inertial frame. Moreover, you may now retrieve states
relative to non-inertial frames.
For example suppose you want to determine whether or not Jupiter is
above the local horizon at the Goldstone tracking site. The following
code fragment allows you to make this determination at an epoch ET. Note
we've hard-coded the radii for the spheroid that approximates the
surface of the earth.
C Look up the bodyfixed state of Jupiter relative to
C the Goldstone tracking site and the state of
C Goldstone relative to the center of the earth.
C
CALL SPKEZR ( 'JUPITER', ET, 'IAU_EARTH', 'LT+S',
. 'GOLDSTONE', JSTATE, LT )
CALL SPKEZR ( 'GOLDSTONE', ET, 'IAU_EARTH', 'NONE',
. 'EARTH', GSTATE, LT )
C
C Compute the local surface normal at the Goldstone site.
C
EQRAD1 = 6378.140
EQRAD2 = 6378.140
POLRAD = 6356.75
CALL SURFNM ( EQRAD1, EQRAD2, POLRAD, GSTATE, LNORML )
C
C Next compute the angle between the local normal and the
C vector to Jupiter. If the angle is less than pi/2 then
C Jupiter is above the local horizon. Otherwise it's not
C visible.
C
ANGLE = VSEP ( JSTATE, LNORML )
IF ( ANGLE .LT. HALFPI() ) THEN
WRITE (*,*) 'Jupiter is above the horizon.'
ELSE
WRITE (*,*) 'Jupiter is not visible from Goldstone.'
END IF
Below is a list of the non-inertial frames that are currently supported.
Frames that begin with the letters IAU are frames whose orientation is
specified in the report: "Report of the IAU/IAG/COSPAR Working Group on
Cartographic Coordinates and Rotational Elements of the Planets and
Satellites"
IAU_ADRASTEA
IAU_AMALTHEA
IAU_ANANKE
IAU_ARIEL
IAU_ATLAS
IAU_BELINDA
IAU_BIANCA
IAU_CALLISTO
IAU_CALYPSO
IAU_CARME
IAU_CHARON
IAU_CORDELIA
IAU_CRESSIDA
IAU_DEIMOS
IAU_DESDEMONA
IAU_DESPINA
IAU_DIONE
IAU_EARTH
IAU_EARTH_BARYCENTER
IAU_ELARA
IAU_ENCELADUS
IAU_EPIMETHEUS
IAU_EUROPA
IAU_GALATEA
IAU_GANYMEDE
IAU_HELENE
IAU_HIMALIA
IAU_HYPERION
IAU_IAPETUS
IAU_IO
IAU_JANUS
IAU_JULIET
IAU_JUPITER
IAU_JUPITER_BARYCENTER
IAU_LARISSA
IAU_LEDA
IAU_LYSITHEA
IAU_MARS
IAU_MARS_BARYCENTER
IAU_MERCURY
IAU_MERCURY_BARYCENTER
IAU_METIS
IAU_MIMAS
IAU_MIRANDA
IAU_MOON
IAU_NAIAD
IAU_NEPTUNE
IAU_NEPTUNE_BARYCENTER
IAU_NEREID
IAU_OBERON
IAU_OPHELIA
IAU_PANDORA
IAU_PASIPHAE
IAU_PHOBOS
IAU_PHOEBE
IAU_PLUTO
IAU_PLUTO_BARYCENTER
IAU_PORTIA
IAU_PROMETHEUS
IAU_PROTEUS
IAU_PUCK
IAU_RHEA
IAU_ROSALIND
IAU_SATURN
IAU_SATURN_BARYCENTER
IAU_SINOPE
IAU_SUN
IAU_TELESTO
IAU_TETHYS
IAU_THALASSA
IAU_THEBE
IAU_TITAN
IAU_TITANIA
IAU_TRITON
IAU_UMBRIEL
IAU_URANUS
IAU_URANUS_BARYCENTER
IAU_VENUS
IAU_VENUS_BARYCENTER
|


public static final class R.id
extends java.lang.Object
| Constructor and Description |
|---|
R.id() |
public static final int Platform
public static final int Private
public static final int Quality
public static final int Title
public static final int acceptTrade
public static final int action_settings
public static final int addImageCapture
public static final int addImageGallery
public static final int addTraderButton
public static final int button3
public static final int button4
public static final int button9
public static final int cancelButton
public static final int cancelfriendofferinventory
public static final int cancelitemsFromFriendInventory
public static final int cancelitemsFromMyInventory
public static final int changeCity
public static final int changeEmail
public static final int changeName
public static final int changePhone
public static final int consoleSpinner
public static final int contactTextView
public static final int counterFriendInventoryButton
public static final int counterMyInventoryButton
public static final int counterSaveButton
public static final int counterfriendofferinventory
public static final int counteritemsFromFriendInventory
public static final int counteritemsMyInventory
public static final int countertextmyinventory
public static final int currentTrades
public static final int decidefriendofferinventory
public static final int decideitemsFromFriendInventory
public static final int decideitemsFromMyInventory
public static final int deleteItemMenuId
public static final int description
public static final int descriptionBox
public static final int done
public static final int editGameText
public static final int editGameTitle
public static final int editItemMenuId
public static final int editItemSaveButton
public static final int editProfile
public static final int editReleaseDate
public static final int editconsoleSpinner
public static final int editdescriptionBox
public static final int editprivatepublicSpinner
public static final int editqualitySpinner
public static final int email
public static final int email_user
public static final int friendInventory
public static final int friendInventoryButton
public static final int friendInventoryDone
public static final int friendInventoryListView
public static final int friendTradeButton
public static final int frienddone
public static final int friendlistView
public static final int friendofferinventory
public static final int friends
public static final int gameImageView
public static final int gameTitle
public static final int imageButton
public static final int imageView
public static final int imageView1
public static final int inventory
public static final int itemsFromFriendInventory
public static final int itemsFromMyInventory
public static final int l
public static final int lblListHeader
public static final int lblListItem
public static final int location
public static final int locationDescription
public static final int locationImage
public static final int locationItem
public static final int locationItemButton
public static final int locationTextView
public static final int loginButton
public static final int mineInventoryListView
public static final int myInventoryListView
public static final int my_profile
public static final int myinventorycancelview
public static final int myinventorycounterview
public static final int myinventorydecideview
public static final int myinventorytradeview
public static final int nameTextView
public static final int newItemPicture
public static final int newItemPictureView
public static final int newgametext
public static final int pastTrades
public static final int pasttradeListView
public static final int pendingtradeListView
public static final int privatepublicSpinner
public static final int qualitySpinner
public static final int registerButton
public static final int releaseDate
public static final int releaseDateEdit
public static final int removeFriendMenuId
public static final int removeTraderButton
public static final int saveButton
public static final int scrollView
public static final int searchView
public static final int searchViewFriend
public static final int selectItemtoTrade
public static final int selectfriendItemtoTrade
public static final int showFriend
public static final int showPeople
public static final int textView
public static final int textView12
public static final int textView13
public static final int textView14
public static final int textView15
public static final int textView16
public static final int textView17
public static final int textView19
public static final int textView20
public static final int textView24
public static final int textView3
public static final int textView4
public static final int textView5
public static final int textView6
public static final int textView7
public static final int textView8
public static final int textView9
public static final int tradeFriendMenuId
public static final int tradeOffers
public static final int traderCityTextView
public static final int traderEmailTextView
public static final int traderNameTextView
public static final int traderPhoneTextView
public static final int tradingRequestButton
public static final int userCityTextView
public static final int userEmailTextView
public static final int userNameTextView
public static final int userPhoneTextView
public static final int user_city
public static final int user_phone_num
public static final int username
public static final int viewFriendProfileMenuId
public static final int viewItemDate
public static final int viewItemDesciption
public static final int viewItemName
public static final int viewItemPlatform
public static final int viewItemQuality
public static final int viewStatus


-
Google Discussiegroepen
groups.google.com
Met Google Discussiegroepen kun je online forums en e-mailgroepen maken en eraan deelnemen. Bovendien profiteer je van uitgebreide ...
-
If programming languages were weapons • Bjorn Tipling
bjorn.tipling.com
C is an M1 Garand standard issue rifle, old but reliable. C++ is a set of nunchuks, powerful and impressive when wielded but takes many years of pain ...
-
Breaking News, World News & Multimedia
www.nytimes.com
The New York Times: Find breaking news, multimedia, reviews & opinion on Washington, business, sports, movies, travel, books, jobs, education, real ...
-
The Official Microsoft ASP.NET Site
www.asp.net
ASP.NET is a free web framework for building great Web sites and Web applications using HTML, CSS and JavaScript.
-
xkcd: Tasks
xkcd.com
Warning: this comic occasionally contains strong language (which may be unsuitable for children), unusual humor (which may be unsuitable for adults), ...
-
Apple Shows Love for HTML5 with iOS 8 | Blog | Sencha
www.sencha.com
September 16, 2014 | Ross Gerbasi
-
A Watch Guy's Thoughts On The Apple Watch After Seeing It In The Metal ...
www.hodinkee.com
I'm not even sure we can call it a watch. Okay, it goes on the wrist, and it happens to tell the time, but that's about where the similarities ...
-
Coursera
www.coursera.org
Take free online classes from 80+ top universities and organizations. Coursera is a social entrepreneurship company partnering with Stanford ...
-
My year with a distraction-free iPhone (and how to start your own ...
medium.com
In 2012, I realized I had a problem: Infinity in my pocket was too much.
-
Medium’s CSS is actually pretty f***ing good.
medium.com
Some notes on Medium’s CSS, the steps we’ve taken to get it to where it is, and the world we live in today.
-
Humans Need Not Apply
www.youtube.com
Discuss this video: http://www.reddit.com/r/CGPGrey/comments/2dfh5v/humans_need_not_apply/ http://www.CGPGrey.com/ https://twitter.com/cgpgrey ## ...
-
How to Be Polite
medium.com
Most people don’t notice I’m polite, which is sort of the point. I don’t look polite. I am big and droopy and need a hai…
-
How we make RWD sites load fast as heck | Filament Group, Inc., Boston, MA
filamentgroup.com
At Filament Group, We design engaging sites and apps for mobile, tablet, desktop and beyond that are simple to use and accessible to everyone.
-
Breach - A browser for the HTML5 era
breach.cc
Everything in the browser is a module, a web-app running in its own process. Construct your own browsing experience by selecting the right modules ...
-
Troy Hunt: Everything you need to know about the Shellshock Bash bug
www.troyhunt.com
Observations, musings and conjecture about the world of software and technology
-
PHP: rfc:isset_ternary
wiki.php.net
PHP is a web-focussed programming language, so processing user data is a frequent activity. In such processing it is common to check for something's ...
-
Introducing Runnable JavaScript, CSS, and HTML Code Snippets « Blog – ...
blog.stackoverflow.com
On Stack Overflow and our other code-related sites, creating a minimal, complete, and verifiable example is the best way to get an answer to your ...
-
Android Browser flaw a “privacy disaster” for half of Android users
arstechnica.com
Bug enables malicious sites to grab cookies, passwords from other sites.
-
From Indonesia To Turkey New Archaeological Discoveries Uncover The ...
www.grahamhancock.com
An article by Graham Hancock on The Mysteries Of A Lost Civilisation
-
Presented at CSSConf.eu, September 2014. You've learned the concepts, now ...
speakerdeck.com
CSS Performance Tooling
-
Apple
www.apple.com
Apple designs and creates the iPhone, iPad, Mac notebooks and desktop computers, iOS 8, OS X, iPod and iTunes, and the new Apple Watch.
-
Battle For The Net
www.battleforthenet.com
Cable companies want to slow down (and break!) your favorite sites, for profit. To fight back, let's cover the web with symbolic "loading" icons, to ...
-
Centering in CSS: A Complete Guide | CSS-Tricks
css-tricks.com
Centering things in CSS is the poster child of CSS complaining. Why does it have to be so hard? They jeer. I think the issue isn't that it's ...
-
Video: https://www.youtube.com/watch?v=LaxbdIyBkL0 Presented at at the ...
speakerdeck.com
JavaScript Memory Management Masterclass
-
The Technology behind Hyperlapse from Instagram
instagram-engineering.tumblr.com
Yesterday we released Hyperlapse from Instagram—a new app that lets you capture and share moving time lapse videos. Time lapse photography is a ...
-
Coming Soon: CSS Feature Queries | Web Platform Team Blog
blogs.adobe.com
Feature Queries are part of the CSS3 Conditional Rules specification , and offer a native method of testing for CSS feature support. You can use ...
-
Living with Web Apps - Tales of a Developer Advocate
paul.kinlan.me
As a Developer Advocate for Google Chrome and the Web it is my job to build a picture of how the Web works and educate developer on how to build for …
-
HTTP Shaming
httpshaming.tumblr.com
Can you please encrypt my traffic?! Yup, this site is on HTTP – blame Tumblr for not supporting SSL,...


I am a 21 year-old studying Informatics at the University of Michigan. This interdisciplinary major between the
the College of Engineering, Department of Statistics and School of Information combines a study of human computer interaction,
big data analysis, and software development.
Through my studies and work experience, I cultivated my programming skills together with an understanding
of how users interpret and understand what I create.
I aspire to design and develop things that change people's lives in a positive way, whether it is
making a mundane task easier or completely revolutionizing the way technology is involved in our lives.
I have experience with every step of the design process. Starting with usability research and designing interfaces that ensure the best user experience to implementing specifications while following best practices.
I can build fully featured, scalable web applications using PHP (CakePHP) and Node.JS (Express). My developed applications include professional and personal projects. I am always looking for the next API or web technology to hack on.


Girl, 13, left with deep burns after charging phone falls in her bath
The girl was in the bath in Amsterdam, when she dropped her phone into the water, prompting her mum to run in and wrench her out
by Milo Boyd, https://www.mirror.co.uk/authors/milo-boyd/A teenage girl was electrocuted when her smartphone fell into the bath while charging.
The 13-year-old girl screamed out in pain after the phone sparked in the water, prompting her mum to run into the bathroom.
The Dutch girl was pulled out of the bath by her mother, who called the emergency services when her child was clear of the bathtub.
When paramedics arrived at the home they punched the girl in the sternum in a successful bid to wake her up.
She spent two days in hospital where she later received surgery to help heal the deep burns on her hands and stomach.
The unnamed teenager's lucky escape has inspired doctors at Vrije Universiteit Medical Center in Amsterdam, where she was treated, to write about the dangers of using phones in the bath.
"Risks of electrical devices in household use are underestimated," they wrote in the Journal of Medical Case Reports.
"Although products are thoroughly tested and certified, they pose a great danger if used inappropriately.
"A severe electrical burn injury can cause destructive injury with high morbidity, lifelong scars and even death."
Although the doctors did not accompany their warning with specific figures, they said growing smartphone usage amongst minors was making them more prone to electric shocks.
The traumatic nature of the accident left the girl with amnesia and no clear idea about how she was electrocuted.
Doctors have theorised that the seriousness of her injuries meant she was electrocuted by a phone connected to the the mains supply.
The combination of the 240V electricity that runs through the mains supply in the Netherlands, along with moist, less resistant skin, means the accident could have proved fatal.
Fortunately the quick thinking mum was on hand to unplug the phone as soon as she got into the bathroom.
The wounds on the girl's hands healed after a week of fusidic acid cream treatment.
Her oval-shaped burns proved harder to shift and had to be surgically rejected three weeks after the accident.
In September, a Russian actress died after the phone she was charging fell in the bath.
Evgenia Shulyatyeva , 26, died within minutes after the device fell into the water she was in.
Her heartbroken mum Vera found her dead at her home in Kirovo-Chepetsk, west Russia.