We soon realized that we could not run with a front support like the 216 , as the nacelle is in the way and the prop is to close to the front edge of the nacelle. So we designed extra bracing for the rear mounting frame, then passed that over to to Dom and he cut it out on his CNC Plasma cutter.
We used 5 mm steel to make the extra side mounts with internal gussets .
Then a couple of extra stays back on to the lower frame.
We plan to mount the tanks more to the side , which will cover up the extra steel work and leave the center section open so the rear of the engine is visible.
New Tank mounts have been made just like on the 216 but offset to the outside.
Note the extra casing that is fitted to this 759 to allow electrical connection to the prop hub,as there is limit switches inside to allow interlocking for prop thrust reverse.
With my very helpful wife Gill the prop hub and one blade was mounted to check clearances. As you can see the blade in full feather would touch the frame. After a bit more measuring , we decided that 60 mm needed to come out.
After Chopping the frame back by 60 mm, it was all clamped back up and welded up. Next job make up the tanks.
At the shows, there is always two questions asked from young and old.
So we decided to make a display unit that can be taken to shows and people can have a hands on demonstration of both of these questions.
We had a old 264 engine that we had removed all useful parts, so we decided to use this to make our display unit. First I cut up the front crank case section then the timing case cover using a reciprocating saw.
Next job was to weld back together the master rod, as this had to be cut to strip the engine as that cylinder would not come off.
Next I cout down the front half of the crank manaton and make a replacement crank pin to allow the master rod to be attached.
The last job was to make a cranking handle , it works a treat. Over winter Pete will tidy the casing up and crankshaft on the milling machine, then all we have to do is make a perspex box to go over it , as there is plenty of finger trapping gears and sleeve valve ports etc.
On the Sunday we invited an 93 year old Halifax Pilot of 102 squadron Tom Sawyer to start up our 216, we didn't have to ask him twice! he was chuffed to bits.
The next outing for us was at the Duxford Flying Legends 11th and 12th of July, before we went down we made a new tachometer from a Land Rover defender speedo. and a new air intake and fit some new guages.
We modified the Land Rover speedometer drive spindle to fit the square drive on the Hercules, then made a brass bush to hold it in.
And here we have the finished article, the original tachometer drive altered to drive a Land Rover speed transducer which then drives a 80mm Land Rover Defender speedometer, we used a pulse multiplier bought from ebay to allow us to calibrate the speedometer.
We used an old Snapon timing light to calibrate the tachometer.
The next job was the air intake.
This was made from a stainless steel 6″ bend split in two then spaced out to suite the intake.
Pete made up a flange on the milling machine to fit the engine.
Once welded up and polished , it certainly looks the part.
We then fitted some new Gauges and a new cover over the hydraulic controls for the trailer .
We had a great weekend down at the Duxford flying legends where we got through a lot of Av-Gas! Before we went down we fitted a couple of brass plaques, One for my Dads crew and the other for Peter Blackburn's Dad.
We ran the engine every 45 mins during Saturday and Sunday up to 13:00 just before the Air Show starts, It certainly drew a lot of attention.
After Duxford our next show was a local three day family music festival called the DeerShed Festival only two miles away.
Last year we took the 216 just to show it as a static display, and the amount of people that asked us when we were going to start it! so this year we were invited back to run the engine and it was great success.
We decided before the DeerShed festival that we would take the 759 with us also, so this meant getting it out of the pod and mounted on a frame! nothing like a bit of pressure, we only had two weeks to do this!
The first job was to make another frame.
After a dry fit of the steel work, Pete milled in the mounting holes for the engine mounts.
The first time the 759 has seen daylight since 1971, even as Peter was watching the engine come out of the pod a Swallow had a fly by.
When we got the engine fitted to the frame , it was time to re-hydrate the engine before we lifted it onto a trailer ready to take to the show.
At the show we fitted a full size Rotol Prop, this has put an idea into our heads, should we design a frame to fit a 14 tonne truck so we can run a full size prop at some time!
At the end of the show a friend of ours Ben Potter brought his 9 foot wingspan Steller's Sea Eagle called Camillia over to have it's picture taken next to the Hercules with all of our Grand Kids and friends . Ones born to fly ones built to fly!
Our next trip out took us to the Scottish Borders Agriculture Show at Duns on the 1st of August.
A lot of local people had a lot of knowledge of the engine as there was two local Airfields that used to be home to Beau-fighters.
At the Show there was a 1944 David Brown Airfield tractor tug, so thought that we would introduce them!
A young future pilot i think!
After the engine run,Gill my wife did a bit of house keeping and cleaned the prop blades.
Our next job is to sort out the 759, when we had the full size prop on it , we tried to turn it, it was stuck!.
It looks like this one had missed the inhibiting oil!, we have took the head off and the sleeve is too rusty, so we will have to renew that one.


Background: Erythropoietic protoporphyria (EPP) is an inherited disorder that has been described as autosomal dominant with incomplete penetrance (Todd 1994). Patients present in childhood with photosensitivity as a result of a defect in heme biosynthesis causing accumulation of protoporphyrin (DeLeo et al. 1976). Mutations in ferrochelatase (FECH), the terminal enzyme of the pathway, are observed in both affected and asymptomatic individuals. Affected individuals, however, appear to have an enzyme deficiency of >50%, which has recently been attributed to a common polymorphism (IVS3-48T/C) on the "wildtype" allele that leads to reduced expression of the allele (Gouya et al. 1996; Gouya et al. 2002). Aim: To characterise a cohort of 13 affected South African EPP individuals at molecular level and to assess the frequency of the IVS3-48C polymorphism in this cohort and a control population. Methods: PCR amplification and subsequent single-stranded conformational polymorphism (SSCP) analysis of the coding region and surrounding intronic sequences of FECH was carried out. Fragments showing an altered pattern were sequenced to identify the mutation. Various enzymes were employed in restriction enzyme digestion in order to screen for identified changes including the IVS3-48T/C polymorphism. Results: A novel 7bp deletion in exon 4 of FECH has been identified in a single individual and a previously described 5bp deletion in exon 7 has been observed in eight individuals in the cohort. Both cause a frameshift and a premature stop codon within 100 amino acids of the deletion. A novel change, namely IVS10-61G/A, was identified although the functional significance has yet to be determined. The frequency in the population has not been determined but unaffected control individuals have been shown to carry the change suggesting that it is a common polymorphism. The IVS3-48C polymorphism was found to be present in 11 of the 13 affected individuals and 10.78% of the matched control population. Discussion: The prevalence of the deletion identified in exon 7 for the majority of patients strongly suggests a founder effect in the South African EPP population. Family studies will allow us to determine whether this mutation is indeed the result of a single ancestral event. The low expression allele appears to play a role in the manifestation of the disease in our population as proposed for the French population.


Vibroacoustic analysis is put to use in order to increase reliability and objectivity of condition monitoring of all bearings and reduction gear of wheel motor units of ER-2 electric multiple unit.
The COMPACS®-EXPRESS system ensures evaluation of current technical condition and prediction of future technical condition of the elements of wheel motor unit by the results of measurement of vibration parameters, determines quantitative characteristics of physical quantities used as diagnostic features, displays them on the screen as a special board which shows quantitative and qualitative characteristics of the feature.
At the same time built-in expert system displays on the screen text and graphical information on a technical condition of wheel motor unit according to the test results. A printing device records this information, and the test results are automatically archived in the form of test reports.
Implementation of the COMPACS®-EXPRESS system for vibration analysis enables to improve the quality of repair and reliability of electric stock.


text:
BEST SELLERS - METAL DETECTORS
View Garrett Metal Detectors
VIEW Fisher Metal Detectors
Is Metal Detecting for Me?
Metal Detecting Terminology
Metal Dectecting Clubs - California
Treasure Hunting in California - Metal Detecting in Ca
Metal Detecting Stories
Metal Detecting Equipment
Amateur With Metal Detector Finds Gold Hoard - VIDEO
Home > Gold Mining Equipment > New Items and Best Sellers > BEST SELLERS - METAL DETECTORS > Metal Detectors for Sale > Metal Detecting Equipment > Treasure Hunting in California - Metal Detecting in Ca > California Gold Panning & Gold Prospecting > Gold Panning Yosemite > California Gold Country - Exploring, Prospecting for Gold > Southern California Gold Mining Info - Tour > Finding Gem Stones in California
Home > Gold Prospecting - FREE TIPS > Panning For Gold > Gold Prospecting EQUIPMENT (SEE ALL) > Gold Mining Equipment > New Items and Best Sellers > BEST SELLERS - METAL DETECTORS > Metal Detectors for Sale > Metal Detecting Equipment > Treasure Hunting in California - Metal Detecting in Ca > California Gold Panning & Gold Prospecting > Gold Panning Yosemite > California Gold Country - Exploring, Prospecting for Gold > Southern California Gold Mining Info - Tour > Finding Gem Stones in California
GARNET - Gem- and specimen-quality white to pale green grossularite garnet occurs on Indian Creek in Siskiyou County and along Traverse Creek near Georgetown in Eldorado County. Other locations for these types of grossularites are the south side of Watts Valley in Fresno County, near Selma in Tulare County, near Big Bar in Butte County and near El Toro in Orange County. Some of the finest quality spessartite garnet known come from pegmatites in San Diego County. Spessartites have been found on Gem Hill near Mesa Grande and in mines in the Rincon and Pala Districts. The most productive area with the finest quality garnets is on the western side of Hatfield Creek Valley near Romona. Near Indian Head Hill in San Diego County is a deposit of fine-quality hessonite garnet, and another deposit is near Dos Cabezas.
AGATE - California's "Mojave Blue" agate has gained a great deal of attention in the past several years. This pastel blue or blue-gray agate cuts into attractive cabochons for jewelry and, in the hands of an expert carver, makes outstanding carvings.
Specialty Stones - Deposits in the State are blessed with a variety of collector/specialty stones. Stones have been cut from fine-quality, pink apatite from San Diego County. Some small colorless stones have been cut from analcine, but the location from which the material was recovered is unknown. Fine-quality, brown colored stones have been cut from axinite from deposits in Calaveras, Madera, Riverside, and San Diego Counties. Benitoite, the State gemstone, is the collector/specialty stone for which the State is best known. San Benito County is the only source of this fine, blue colored gem. Large, fine-quality, light to medium green colored stones can be cut from fluorite found in Los Angeles County. Large, colorless stones are cut from scheelite from deposits in Kern and Inyo Counties. Nearly flawless, colorless stones have been cut from natrolite from San Benito County. The author also has seen natrolite stones that were labeled as being from Los Angeles County. Deposits in the State also yield fine-quality, brown epidote, colorless calcite and colemanite, and augelite.
QUARTZ CRYSTALS - Deposits in California are another source of significant amounts of quality quartz crystal. For many years cobbles and round crystals have been found in streambeds in Amador and Calveras Counties. The best quality, largest, and most abundant crystals come from ancient stream channels in the Mokelumne Hill area of Calveras County. Over the years, various mines in the area have produced thousands of kilograms of rock crystal, with some of the individual crystals weighing as much as 275 kilograms and many of the crystals measuring more than 600 millimeters in length and 250 millimeters in diameter. The American Museum of Natural History has a 150 millimeter sphere cut from a Mokelumne Hill rock crystal. Additionally, the pegmatites of Hiriart Hill, San Diego County, have produced hundreds of kilograms of fine-quality rock crystal from which a number of 60 to 90 millimeter spheres have been cut.
TOURMALINE - Tourmaline was, until recently, the single largest contributor to the value of gemstones produced from California. And for the past 5 years, California has ranked as high as second and as low as sixth in the value of natural gemstone produced in the United States. The State's fabulous tourmalines were discovered by the gemstone industry in the late 1870's or early 1880's. The caveat, discovery by the gemstone industry, is used because Native Americans discovered and used these beautiful tourmalines long before that.
Since their discovery, the tourmaline deposits in Riverside and San Diego Counties have had more tourmaline produced and of greater value than any other deposits in the Northern Hemisphere. In fact, it is probable that only the deposits in Brazil have been more productive.
One of the reasons for the productivity of the area is the longevity of the individual mines. Many of them have operated intermittently from the 1890's until the present. The famous Himalaya Mine is quite likely the best example.
Records indicate that from 1898 until 1914, the Himalaya was the world's largest producer of tourmaline. Furthermore, the records indicate that in 1904 production from the mine was at least 5.5 metric tons. In 1989, 84 years later, a single pocket in the mine produced more than 0.5 metric ton of tourmaline.
The history of production from the mine is not one of steady continuous operation. The mine operated continuously from 1898 until 1914, after which it operated sporadically until 1952. At this time, it once again began continuous operations that lasted until 1964 when it returned to intermittent operation until 1977. Since then the mine has been in operation under the direction of Pala International.
California tourmalines come in all colors except certain shades of blue and yellow. They also occur in bicolors, tricolors, and concentrically and laterally zoned combinations. Crystals vary in diameter from about 3 millimeters to as much as 125 millimeters, and vary in length from about 12 millimeters to as much as 250 millimeters.
Because of the large size of the crystals available, some large stones have been cut from California tourmaline. A 400-carat pink-red stone has been cut, as well as a flawless 75 carat green to pink bicolor and flawless 30- to 40 carat green to colorless to pink tricolored stones.
California deposits should continue to produce quantities of faceting, carving, and cabochon grade, as well as specimen-grade tourmalines for some time into the future. In late 1992, a new deposit of tourmaline was discovered in Riverside County that could result in greater production over even a longer period of time.
TURQUOISE - The production of turquoise from deposits in California can be traced back to pre-Colombian Native Americans. Prehistoric mining tools have been found in some of the old workings of the turquoise mines in San Bernardino County.
Over the years, the State's deposits have produced a substantial amount of turquoise. Deposits are located in San Bernardino, Imperial, and Inyo Counties. The material occurs as nodules and as vein filling. Most of the nodules are small in size, about the size of the end of your thumb, and the vein material is about 4 millimeters thick. In the better grade materials, the color varies from a pale to a dark blue, poorer grade materials are greenish-blue and green in color. Some of the material has yellow-brown limonite spiderwebbing.
In the past, a number of turquoise mines operated in the State, several or more mines in each of the counties. Today, only a single mine, the Apache Canyon Mine, is commercially producing turquoise. Material from the mine is a fine blue color, hard, and takes a good polish.
Article courtesy of www.treasurefish.com
california-minerals
California Gold Panning & Gold Prospecting
Dreaming Big in California
Finding Gem Stones in California

redpajama_set_name: RedPajamaCommonCrawl


text:
Q: Converting Excel Formula involving *OR to TSQL I'm trying to convert this formula into T-SQL.
=IF(D6>F6,D6-C6-1,F6-C6-1)*OR(IF(F6-C6-1<0,0,F6-C6-1))

Does anyone know what the *OR actually means?
The columns C, D, F are all Date fields.
For example

For the first line, this part of the formula IF(D6>F6,D6-C6-1,F6-C6-1) returns 35 and the second part of the formula IF(F6-C6-1<0,0,F6-C6-1) returns 35 as well. So shouldn't the result be 35 x 35 = 1225. The correct answer is 35 however.

A: As per my earlier comment:
The second parameter in the OR would be optional. As a matter of fact, or will just return 'TRUE' if any of it's paramaters is 'TRUE', no matter the amount of (optional) parameters you use. The 'OR' in this case just evaluates the outcome of the second 'IF' (which is 35). So > 'OR(35)' which evaluates to TRUE. Since you multiply this will again evaluate to '35*1' being your final result. The formula is looking strange because 'OR' would always return true in this case. The formula might as well just be '=IF(D6>F6,D6-C6-1,F6-C6-1)'

redpajama_set_name: RedPajamaStackExchange


8-11 year olds, 12-15 year olds and age 15+. We are based on the 3rd floor of the YMCA in Swansea City Centre however also have academies in Bridgend and West Cross.
To find out more information please contact us!
FIRST MONTH OF TRAINING IS FREE!


Our board has being elected to assist in determining the St Phil's mission and purpose. They support and evaluate the Chairman with the goals of the organization in mind. to ensure success of the all areas of the organization as a group they ensure effective organizational planning. Regular monthly meeting are held with this team as well.


Please DO NOT email concerning Accommodation (please ring the club 01332 205018).
Please make sure that your Question is not already answered by using the FAQ/ RULES /DRESSCODE pages before contacting us .
Please do not email asking if you can attend / we cannot answer that question for you .


A share is a basic unit of ownership in a company. When you buy a share you become a part owner of a company. The ownership of the company may be divided into millions of parts, and each part is called a share. People will buy a number of shares as ownership, which gives them part ownership as a shareholder.
All shareholders wholly own the company, but the directors of the company run it on behalf of the shareholders. When you buy shares in a company you are actually buying part ownership and the unit (called shares) represents this part ownership.
For example, if a new company opened and it was going to sell 1000 shares and you bought 500 shares, you would be 50% owner of that company.
Shares are regarded as a paper investment. When you invest in shares through the stock market, you get a piece of paper in return for your money. The piece of papers says you own or have an interest in part of that company. This means that your investment is only as good as that company.
What are Long and Short Dealings?
What is a 'Bonus Issues'?


text:
Q: Why does this happen with Python's list.sort? Given the code:
a=['a','b','c','d']
b=a[::-1]
print b
c=zip(a,b)
print c
c.sort(key=lambda x:x[1])#
print c

It prints:
['d', 'c', 'b', 'a']
[('a', 'd'), ('b', 'c'), ('c', 'b'), ('d', 'a')]
[('d', 'a'), ('c', 'b'), ('b', 'c'), ('a', 'd')]

Why does [('a', 'd'), ('b', 'c'), ('c', 'b'), ('d', 'a')]  change to [('d', 'a'), ('c', 'b'), ('b', 'c'), ('a', 'd')]?

Similarly, given:
c.sort(key=lambda x:3)#
print c

It prints:
[('a', 'd'), ('b', 'c'), ('c', 'b'), ('d', 'a')]

Nothing changes - why?

A: because x[1] means second
use
c.sort(key=lambda x:x[0])

A: You've sorted c using the second item as the key, and the second item does indeed go up, just as you asked for it to go up.  What's so surprising?!

A: from operator import itemgetter
c.sort(key=itemgetter(0))

A: As the others have said, [1] refers to the second element, so the elements in the first part are sorted that way.
As for the second part, list.sort() is stable, so elements that evaluate to the same key will maintain their relative position in the sequence. This is why using .sort(reverse=True) can give different results from .sort() followed by .reverse().

A: You've sorted the list using the second element of each tuple as a key so you get the tuples ordered by their second element (Notice the 'a', 'b', 'c', 'd' in increasing order). What's the problem?


Great for all kinds of polishing & buffing.
Use on paint, fiberglass, plastics, all metals.
Motorcycles – rims, spokes, engine, etc.
Washable up to 30 times.
Made of Italian felt – no overheating or burning.
More economical than lambs wool pads.


text:
Le boulevard de l'Europe est un projet d'artère située dans le quartier Malakoff - Saint-Donatien, à Nantes, en France.

Description
Ce boulevard qui devrait être d'une longueur d'environ , débuterait depuis le boulevard de Berlin, au niveau de la place du Bihoreau-Gris et longerait les voies ferrées de la gare de Nantes, passant devant la façade nord de la gare sud pour rejoindre le quai Malakoff. Sur son tracé, elle doit rencontrer l'allée de Bristol et la rue Marcel-Paul.

Dénomination
Son nom a été adopté à la suite d'une délibération du conseil municipal du 9 février 2018, reprenant la dénomination d'un ancien boulevard qui avait été créé lors de l'aménagement de la cité HLM de Malakoff à la fin des années 1960 (délibération du 30 juin 1969), mais qui fut supprimé à la suite du projet de renouvellement urbain Malakoff-Pré Gauchet lors d'une délibération du conseil municipal du 31 mars 2017.

Historique

Voies latérales

Allée de Bristol
Le conseil municipal approuve, le 5 octobre 2012, l'attribution de ce nom en référence à la ville de Bristol qui fut capitale verte de l'Europe en 2015. Cette voie doit relié le boulevard de l'Europe à celui de Berlin.

Notes et références

Coordonnées des lieux mentionnés

Articles connexes
 Liste des voies de Nantes

Europe
Odonyme se référant à un continent

redpajama_set_name: RedPajamaWikipedia


This collection of video and suggested resources was so good, we wanted to give it a placement on our site for easy access and sharing opportunities – Wireless Warfare Exposed. Includes ways to protect your family.
These are the recommended websites discussed in the video.
Where to get Shielding Bedding to block RF: (also paint, curtains, fabrics, phone cases).
"Controlling the brain with sound waves: how does it work?
Well, to get straight to the science, the principle of non-invasive neuromodulation is to focus ultrasound waves into a region in the brain so that they all gather in a small spot. Then hopefully, given the right set of parameters, this can change the activity of the neurons.
If you want to get rid of neurons that have gone wild, for example in epilepsy, then you might want to crank up the energy to essentially kill them. But if you want to selectively promote or block the neuronal activity, you need to fine-tune your ultrasound waves carefully.
In other words, there's a difference between ultrasound stimulation used for removing tissue, and ultrasound neuromodulation, which is aimed at controlling neuronal activity without damaging the tissue.
Thank you for taking the time to share all this. I take no issue with most all that you and others have presented on this topic. However, I'm having great difficulty believing that much radiation levels can come from wi-fi routers & cell phones when they draw so very little power. It just seems that the radiation levels emitted from them would be so very low in power to cause any harm to humans, as compared say with microwave towers. Perhaps there is more information available which specifically explains this?


text:
<!- - Join Us Button - ->
<!- - Events Button - ->
More Light Staff and Board
Our Churches and Campus Groups
More Light's Programs
More Light Teach-Ins
FAQ: Teach-Ins
Connecting the Dots: Gender Identity and Sexual Orientation
LGBTQIA+ Youth
Caring for LGBTQIA+ Refugees and Asylum Seekers
Liberation Bible Study
More Light in the World
More Light Ambassadors
Out of Order Documentary
Virtual Pulpit Supply
More Light Annual Report 2019
More Light at GA 223
Why Be More Light?
Become a More Light Member
Become a More Light Church
Update Your Congregation's Information
Become a More Light Campus Group
Update Your Campus Group's Information
Becoming a More Light Church
The Ordination of Alex McNeill
The Ordination of Jess Cook
Bread for the Journey
Shine More Light
More Light Congregational Contribution
Faiths Call the Senate About the Employment Non-Discrimination Act (ENDA)
As people of faith, we understand that there are moments that demand a moral call to action. At this moment, when we have never had a better chance of securing workplace protections for the LGBTQ community, we must heed that call and reaffirm our support for the civil rights of our lesbian, gay, bisexual, transgender and queer brothers and sisters. It is our sacred duty to make heard our demand for critical legislation like the Employment Non-Discrimination Act (S. 815/H.R. 1755).
Tomorrow, Tuesday, September 17th, we invite all More Light Presbyterians to join with other faith communities to call our Senators and urge them to support workplace protections for all. The process is simple:
Dial 1-888-897-0174 to hear talking points and then enter your zip code to connect directly to your Senator. Call back a second time to speak with your other Senator.
While the Civil Rights Act of 1964 prohibited discrimination in the workplace based on race, sex, religion, ethnicity and national origin – and later laws barred discrimination based on pregnancy and disability – there is no federal law that protects the LGBTQ community from discrimination in the workplace. ENDA would fix that gap and finally make it illegal to fire, refuse to hire, demote or fail to promote someone based on their real or perceived sexual orientation or gender identity.
Support for the Employment Non-Discrimination Act is rapidly growing. The bill now has 53 co-sponsors in the Senate – including Republican Senators Mark Kirk (IL) and Susan Collins (ME) – and 177 co-sponsors in the House including three Republican Representatives. Support within the business world is growing as well, with more than 90 major corporations publicly endorsing the bill. Religious groups are speaking out as well; nearly 50 religious organizations signed onto a letter to the members of the HELP committee urging them to vote for ENDA.
According to recent polls 73% of Americans support the workplace protections promised in this legislation (another survey found that 9 out of 10 voters thought these protections already exist!). People in 21 states around the country have proven their support for workplace protection by passing laws that prohibit discrimination based on sexual orientation and in 17 states that prohibit discrimination based on gender identity. These numbers reveal the deep resonance ENDA holds with both our American and religious values.
Workplace discrimination based on sexual orientation and gender identity, characteristics which have nothing to do with job performance, denies members of the gay, lesbian, bisexual, transgender and queer community the full humanity that comes with the ability to earn a living, provide for their families and contribute to society. All of us are diminished when individuals are prevented from reaching their full potential and prohibited from contributing the full measure of their talent and ability to society. The Employment Non-Discrimination Act is so critical precisely because it ensures that our workplaces operate as meritocracies, ensuring that people are judged based on their ability to perform a job, not on their personal characteristics. It ensures that our society recognizes the fundamental truth of our tradition, that all people are created in the in the image of God.
This bill has been introduced in nearly every Congress for the past twenty years, but has not received a vote in the Senate since 1996. But the tide is turning and the prospects for LGBTQ rights and ENDA's passage have never looked better. The Senate Health, Education, Labor and Pensions committee passed ENDA this summer with a strong bi-partisan vote of 15-7. Senate Majority Leader Harry Reid has promised a vote on the bill in the coming months. It is critical that Senators hear from the religious community that this landmark civil rights legislation is our moral imperative as Americans and as people of faith. Can you commit 10 minutes of your day tomorrow to making the call?
September 16, 2013 at 11:48 am Uncategorized Share via:
More Light Presbyterians
8725 Columbine Rd. #44727
Copyright © 2021. Designed by WPlook Studio
Want to stay in touch via text? TEXT 72572 and enter the code 1MLP to sign up! Dismiss


text:
Red Wings May Build New Rink West of Woodward
By BarGal,
June 22, 2006 in Detroit
BarGal
Location: Metro Detroit
I was reading in this week's Crain's (June 19, 2006) about one of the long rumored possible sites to build a new rink would be on this area. It's 15.4 acres and the Ilitch Family already owes 8.9 acres of it. (However, Chris Ilitch says it would be too expensive to buy up the rest.)
When I first saw the map I panicked because I thought that the GAR Building was in that area, but after researching some, I found it is just outside of the proposed area.
Any how, could you imagine the traffic on I-75 if they build it there? It's horrible when there's a Lions' or Tigers' game. Can you imagine what it'd be like if any of the games should fall on the same day at or near the same time?
Location: West Villlage 48214
I still think that cutting off Cass Avenue by building a stadium there is stupid. Why do they need so much land? So they can surround the stadium with surface lots? Watch...they'll want to set the stadium back from Grand River, and then put in a few surface lots right on Grand River so that they can make the stadium look more suburban and totally out of context.
agdomain
http://www.letsgowings.com/forums/index.ph...st&p=850279
Funny, I just posted regarding that exact same area about a new arena on LetsGoWings.com. I am convinced one could fit an arena in that space between Grand River and Cass, although it would be a tight fit. There could be a garage build over Clifford, with some possible type of tram (think Interstate Traveler...) connecting it with the rest of Foxtown & the Comerica lots.
Location: Center City Detroit
Has anyone ever been to the Arena District in Columbus, OH? That is how we should be planning an area for a new rink. Not by gobbling up all the surface streets and some of the buildings that could be preserved if we did. We can get more creative than this, in my opinion.
jsmyers
I like your ideas in general agdomain. It actually isn't that tight of a fit:
Look for my posts here:
"atdetroit . net /forum/messages/62684/64187.html"
(For some reason, the url is getting corrupted by the forum. Take out the spaces in order to get the real URL.)
http://www.urbanplanet.org/forums/index.php?showtopic=20328
Whip out a couple of instances of Google Maps and check it out.
RustTown
There is no reason that a hockey arena needs as much land as Ford Field or Comerica Park. That is just ridiculous. The city should demand that they require at least part of the parking to be put underground. There are two many superblocks in, or going up, on downtown's north end along the freeway (i.e. MGM Grand, this proposed arena, Comerica Park, and Ford Field). This isn't some suburb, is it?
DetroitBazaar
Perhaps they will build the arena. I remember back when Mr. I was going to include it into his new Tiger Stadium plan on the West side(according to the papers), nothing happened except a rise in real estate prices. I actually remember when he was going to build a winter wonderland and build the Hard Rock before Hard Rock came to town too and it made big news! I actually dislike Joe Louis Arena and hope he fronts all the money to build an arena but like others have said, too much land and surface parking won't be something I'd like to see. It would be a shame to see Downtown Detroit turn into some kind of suburban style, isolated island. Aww, what do I know You know, Mr. I and family are geniuses as far as building value out of rumor through the media. Maybe it'll all happen and we can reverse the trend of thousands fleeing the city every year as pointed out in the latest census estimates. 887,000 now, and I find that even a little high. Get ready to salute Grand Rapids as the biggest city in Michigan. Some of that is tongue in cheek. I respect you all.
Peace to you and Peace to Detroit!
hudkina
I always thought the best spot would be to build it between Clifford and Park Ave and Montcalm and Elizabeth.
If that isn't large enough, they could cut across Clifford to Cass, but I would hate to cut up Clifford.
Oh yeah, I definitely get what you're saying. Actually, if you look on Google Maps, you could see that JLA probably fits in that footstep rather easily. As far as the "tight fit" is concerned, I would like to see how a new arena in that space could deal with all of the extra amenities (i.e. parking, etc.). If they did "form fit" the new rink for that area (i.e. putting up walls on Gd River, Cass, etc, and not setting it back from the roads), it would have so much more of that "Detroit style" and alot more class to come with it. Plus, we wouldn't have that sprawlburg-type arena with a mile of parking in all directions.
grrwymg
What's wrong with this:
^ The sad thing is, that probably wouldn't be enough parking for Ilitch! LOL!
I would not touch anything around the Park Avenue District unless it can be guaranteed that none of the streets would be affected and that no (if not few) buildings would have to be demolished.
There is plenty of space in Detroit in prime locations to build an arena. Why is it insisted upon that we have to destroy something in order to make it half-work? Heck, I'd rather put it out in front of the Eddystone/Harborlight lining Woodward.
I agree with you.
But look at the oblique posted above in this thread, and check out my link to previous discussion before.
(http://www.urbanplanet.org/forums/index.php?showtopic=20328)
A new arena can fit into the 2-block space shown in that picture. It can work around the Iodent Building and the existing fire station. BTW - Go to http://local.live.com/ to look at other similar pictures.
One block of a little-used street and 3 small buildings in rough shape would have to be lost (or moved). Those are negative impacts, but not compared to what might happpen. Loosing a block of Columbia isn't like loosing part of Cass or Clifford
There really aren't too many other decent places to put it...especially when you consider Olympia's business concerns.
If you have better ideas, I'm curious to hear them.
Personally, I think MGM, Comerica, and Ford Field have already damaged the street layout enough that fitting it in behind Foxtown wouldn't make much of a difference if they closed off another street or two.
Columbia is the easiest street to close as it isn't a through street in any sense of the world. It doesn't connect to Woodward anymore and all that would be left is a small stretch between Cass and Clifford.
Here's an aerial of the area. There really isn't much left in there any more...it appears that it may already be a lot of surface lots. I do think that the Chin Tiki (where Eminen shot scene for movie "8 Mile"), would be one of the casualties.
resourcefulidiot
chin passed away recently though, so the rennovations pretty much stopped
Marvin Chin had no interest in reopening the place himself anyway. He was doing renovations, but it would've been leased to someone else. The real death knell to the Chin Tiki was when he sold the parking lot next door to the Macedonian Parking Cartel.
Btw, I was invited inside the Chin Tiki recently...what a cool place!
...Btw, I was invited inside the Chin Tiki recently...what a cool place!
I've never been inside the Chin Tiki myself...waaay back in the day, a lot of the teachers and vice principals from Cass Tech used to go there for "lunch."
I used to hang out at Busy Betty Grill, it used to be a couple of buildings north of the Chin Tiki (it was demolished a couple of years ago). Or if Betty was sick or on vacation, we'd go to Chris & Carl's that used to be across the street from the Chin Tiki or Peggy's a burger joint that was on the corner of Cass and the service drive. That's where a lot of the high school kids hung out.
All of these places were in that triangular area that's rumored as a proposed site for for the Wings' new stadium.
Oh Allan, I caught those pics in your Flickr album, great timing there on your part.
Actually, the biggest casualities would be shutting down Cass and/or Clifford, but that doesn't necessarily have to happen if the city demands creative designs in parking and the actual structure if this really is where it's going to go.
BarGal, the Chin Tiki will be open for the last time during the Motor City Tiki event during the weekend of July 22nd. Mark your calendar!
statedude3
Location: Somewhere on Gratiot
The city will hear my voice louder than they will ever desire, if the GAR ends up as a nightclub or something else like that.
As for the arena, what about the stretch where the donovan/sanders buildings were located. I know it is not ideal, but it would serve as a reason to add more housing/businesses further along woodward towards the cultural center. It also would not disturb the street grid.
I could even see a cap on 75 that would connect hockeytown cafe and the arena via a park with a sports theme which could perhaps include monuments to Detroits great sports legends. Personally, the name "arena district" appeals to me much more than "foxtown".
A little off topic, but I've always like central Detroit's "towns" as it's different than many cities. Every city has an arena/stadia(um) district or a this-or-that district. Heck, Lansing is seeking a grant to create a "Stadium District." lol It's so generic.
As a side: You can look up property through the city of Detroit's website(they've actually updated recently, well 2005 last we checked.) Taxes, value, comparisons from buy to sell date, etc. Chin Tiki is there. Seems the value went through the roof when Eminem and crew came in and did their thing with 8 Mile. Mr. Chin just cashed checks as far as we can see. Mr. "I" cashes the ultimate check around those parts in any large land deal. The state of Michigan also has an interesting website describing who owned what and when in that area.
As a side: You can look up property through the city of Detroit's website...The state of Michigan also has an interesting website describing who owned what and when in that area...
Would it be possible to post links to those sites here? I'd like to check them out.


text:
Stodoliszcze () – osiedle typu miejskiego w zachodniej Rosji, centrum administracyjne osiedla wiejskiego Stodoliszczenskoje rejonu poczinkowskiego w obwodzie smoleńskim.

Znajduje się tu stacja kolejowa Stodoliszcze, położona na linii Briańsk – Smoleńsk.

Geografia
Miejscowość położona jest w dorzeczu rzeki Żadownia, przy drodze federalnej R120 (Orzeł – Briańsk – Smoleńsk – Witebsk), 28 km od centrum administracyjnego rejonu (Poczinok), 77 km od stolicy obwodu (Smoleńsk).

W granicach miejscowości znajdują się ulice: 1-ja Bazarnaja, 2-ja Bazarnaja, pierieułok Bazarnyj, Bolszaja Kołchoznaja, Czkałowa, Glinki, Kaczałowa, Kołchoznaja, Krasnoarmiejskaja, Krasnoznamienskaja, 1-yj pierieułok Krasnoznamienskij, 2-oj pierieułok Krasnoznamienskij, Lenina, pierieułok Lenina, Ługowaja, Małaja Kołchoznaja, Miczurina, Nowobazarnaja, Oktiabrskaja, pierieułok Oktiabrskij, Ordżonikidze, 1-yj pierieułok Ordżonikidze, 2-oj pierieułok Ordżonikidze, Pierwomajskaja, Proletarskaja, Puszkina, Raboczaja, Sadowaja, Siennaja, Sowietskaja, 1-yj pierieułok Sowietskij, 2-oj pierieułok Sowietskij, 2-oj pierieułok Sowietskij, Titowa, Twardowskogo, pierieułok Żeleznodorożnyj.

Demografia
W 2010 r. miejscowość liczyła sobie 2973 mieszkańców.

Przypisy

Osiedla typu miejskiego w obwodzie smoleńskim
Miejscowości w rejonie poczinkowskim


text:
Lay's — бренд разнообразных картофельных чипсов, основанный в 1938 году. Чипсы Lay's производятся компанией Frito-Lay, принадлежащей PepsiCo Inc. с 1970 года. Другие бренды компании Frito-Lay включают Fritos, Doritos, Ruffles, Cheetos и брецели Rold Gold. Есть ещё пять видов «Lay's»: «Stix», «Рифлёные», «Stax», «Из печи» и «Maxx».

История бренда
Марку чипсов Lay's придумал американец Герман В. Лэй, начавший свой бизнес в 1932 году мелким коммивояжёром по продаже картофельных чипсов в Нэшвилле. 24-летний коммерсант продавал тогда чипсы Gardner's компании Barrett Food Products, расположенной в Атланте (штат Джорджия).

Лэй был верен торговой марке Gardner компании Barrett Food Products до 1944 года, когда решил изменить название картофельных чипсов на Lay's Potato Chips. Этот год и считается годом рождения торговой марки Lay's.

The Pepsi Cola Company была переименована в PepsiCo в 1965 году после объединения с Frito-Lay, компанией из Далласа, выпускавшей чипсы и другие снеки; эта компания была основана в 1939 году Германом Леем под названием H. W. Lay & Company, в 1959 году она объединилась с компанией Fritos, перед объединением с Pepsi ассортимент продукции Frito-Lay насчитывал 32 позиции, объём продаж превышал 100 млн.

Ссылки
 Сайт компании Frito-Lay
Торговые марки PepsiCo
Появились в 1932 году в США


text:
Q: How to overwrite valo-menu-responsive width-range rules? I need to modify standard valo theme in Vaadin app, so I overwrite standard rules in mytheme.scss (like this), but I want to delete rules for valo-menu width-range in 801-1100px.
For this width-range exist 17 rules in styles.css. Should I overwrite everything rule or may be there are more simple way to do this?
I found just one discussion about this, but answer is not found.


This report documents how to interface a digital camera, frame grabber or telepresence system into the Data Turbine, and thence NEESGrid. Also covered are uses of the live data, debugging tools, and interface methods.
The objective of NEESport is to provide a computational simulation component for the NEESgrid. This is accomplished by providing a Grid Portal for the Open System for Earthquake Engineering Simulation (OpenSees), a software framework for simulating the seismic response of structural and geotechnical systems.
This reference guide is for the NEESgrid File Management Service alias NFMS in the sequel. NFMS is a secure remote web-based archiving system. This means that you may access its files from anyplace on the web.
OpenSees is a software platform for research and application of simulation for structural and geotechnical systems. The OpenSees software framework uses object-oriented methodologies to maximize modularity and extensibility for implementing models for behavior, solution methods, and data processing and communication procedures.
Reference data models have been developed for supporting the major activities involved in earthquake engineering experiments and simulations. The development of NEESgrid data models is based on the experience gained from the review of the state of practice in data representations, data modeling tools, relevant data models, and the suggestions/feedback from the NEESgrid team and the NEES community. Sample data sets have been utilized to demonstrate the features of the data models, along with scenarios for their use. Preliminary validation and usability tests have been performed on the developed reference data model.
This document is an introduction to the Data Turbine and its use in the NEESgrid. The intent is to cover the motivation, design and usage as applied to NEESgrid.
The Electronic Laboratory Notebook is a dynamic Web-based version of the traditional paper laboratory notebook. Collaborators can share their notebooks and use them as a tool for coordinating projects and viewing and analyzing data across the Internet.
This document describes the DataTurbine from Creare augmented with the GSI security layer by Pawel Plaszczak and Krzysztof Wilk from Gridwise Technologies, in May 2004. We present the design, instructions for testing, and the usage use case. Internals are not described due to the confidentiality issues.
This document describes the NEESgrid Reference Implementation, two standard NEES-based experiments which demonstrate the capabilities of the NEES system. This guide will provide an overview of the NEES system, a discussion of the two standard experiments distributed with the NEESgrid software, and an explanation of how to get these experiments up and running.
The purpose of this protocol is to provide for control of simulations by remote applications, particularly in support of multi-site hybrid simulations.
The NEESgrid Teleoperations Control Protocol (NTCP) is used to perform remotecontrol of physical experiments or simulations. An NTCP control plugin is a java classthat implements the interface described in this document to communicate with a controlsystem (or simulated control system). In our NTCP implementation, the NTCP server isconfigured to use a control plugin; when the server receives a request, it performs some"generic" NTCP operations (such as validating the request and updating transaction state)and then makes calls into the control plugin to carry out the request.
This guide is intended to help administrators use tools to create sites, manage users, assign roles and perform other admin-specific functions.
The Creare Data Turbine is by default a holder of transcient data. This document explains how to archive data to disk for subsequent analysis, archiving, backup or replay.
This document serves as an overview of the NTCPclient Toolbox for MATLAB, explaining what the toolbox can do, what is required to use it, some tutorial code snippets to show how it is used, and a reference section documenting each of the functions the user will call.
This document serves as an overview of the NTCPcommon Toolbox for MATLAB, explaining what the toolbox can do, what is required to use it, some tutorial code snippets to show how it is used, and a reference section documenting each of the functions the user will call.
This document serves as an overview of the NTCPmplugin Toolbox for MATLAB, explaining what the toolbox can do, what is required to use it, some tutorial code snippets to show how it is used, and a reference section documenting each of the functions the user will call.
This document is for site programmers wishing to use the data turbine with their own clients or server applications. It gives concrete examples, using basic case, of how to use the RBNB API in the context of NEESgrid.
This document explains how to interface your data acquisition system (DAQ) to the Data Turbine as used in the NEESgrid software distribution. It covers the reference software, direct interfacing, diagnostics and related issues.
This document explains the interactions between the NSDS, driver, and DAQ for the purposes of debugging, replacing the driver or DAQ code, or customizing the DAQ code. In addition to describing in detail the various components that constitute this system, the document also explains protocols and formats associated with data and control channels and data files, as well as error handling and syntax, and provides examples for each. Tools for testing components that have been debugged or replaced are also discussed.
This document describes the NEESgrid File Management Service (NFMS). NFMS provides clients with the ability to archive then locate files independently of how and where they are stored, as well as the ability to negotiate transactions with storage systems. This document describes the release of NFMS included with the 3.0 release of NEESgrid.
This document describes how to plot numberic data, view images and telepresence streams, and run the administrative interface using the Data Turbine viewers that are part of the RBNB package from Creare.
The NEESgrid user interface provides users with access to a range of collaboration and research tools to support the research, practice, and educational goals of the George E. Brown, Jr. Network for Earthquake Engineering Simulation (NEES). This guide is intended to get new users up and running quickly. Developers, equipment site representatives, and advanced users will find additional, more advanced documentation at http://www.neesgrid.org. Additionally, section 7 describes a fictional scenario which demonstrates how the CHEF interface might be used in a collaborative NEES investigation.
NtcpHelper is an NTCP client class. The NTCP protocol itself is described in the NTCP protocol Document; we assume the reader is familiar with that document and with the NTCP protocol.
The objective of NEESport is to provide a computational simulation component for the NEESgrid. This is accomplished by providing a Grid Portal to the Open System for Earthquake Engineering Simulation (OpenSees), a software framework for simulating the seismic response of structural and geotechnical systems.
The Matlab© toolbox FEDEASLab is a user-friendly, versatile and powerful tool for the simulation of nonlinear structural response under static and dynamic loads, which has been used successfully for the development of new elements and material models, as well as for the simulation of the response of small structural models in research and instruction. Its development started in 1998 for the support of instruction of the basic graduate courses of linear and nonlinear structural analysis at the University of California, Berkeley. To date FEDEASLab has evolved into a powerful framework for research in the nonlinear analysis of structures. The toolbox consists of several functions that are grouped in categories and are, consequently, organized in separate directories. These functions operate on five basic data structures which represent the model, the loading, the element properties, the state of the structural response, and the parameters of the solution strategy. A sixth data structure is optional and carries postprocessing information that can be used for response interpretation and visualization.
This document provides a brief introduction to NEES, the George E. Brown, Jr. Network for Earthquake Engineering Simulation, and to NEESgrid, the communications and collaborative software that has been developed for the NEES project. It then describes a NEES-based simulation experiment, performed in July 2003, and shows how some of NEESgrid's features allowed for remote participation in the experiment.
The purpose of this document is to introduce the components that the System Integrator is delivering to the NEES community for constructing and operating NEESgrid. The goal of the document is to provide a description of the NEESgrid components and their intended uses to the people who will be using NEESgrid: especially NEES equipment site operators and the future NEESgrid operations/support team.
This document defines the data model for computational simulation in the NEESgrid system for the George E. Brown, Jr. Network for Earthquake Engineering Simulation (NEES). The objective of the design of the data model is to provide a flexible representation of data for conducting computational simulations using NEESgrid. The simulation data model is closely related to the data model for experimental testing at NEES equipment sites, as developed by Peng et al.
The NEES Metadata Service (NMDS) provides a means of storing, updating, and retrieving metadata objects. The objects can be identified, associated with values, linked, versioned, and protected with access controls. This document describes the NMDS object model. This model is the basis of the design of the NMDS API and its implementation.
The NEESgrid metadata service (NMDS) API provides a means for creating, managing, retrieving, and modifying metadata objects in a NEESgrid repository. This document describes the NEESgrid repository object model, gives an overview of the NMDS API, and demonstrates each major capability of the NMDS API with code examples. This document describes the NMDS API as of NEESgrid release 3.0.
This document is intended for NEESgrid sites wishing to install the supplied code for data acquisition (DAQ) and data handling. It covers getting the code, installation, testing, and some ideas for site customization.
A reference data model for NEESgrid has been designed and developed. The developed reference data model is based on the data requirements for shake table experiments. However, the model is of sufficient generality that major parts of the model can be modified and refined to support other types of experiments, such as centrifuge tests, pseudo-dynamic structural tests, and others. To ensure its usability, validation tests have been conducted by populating the data model with experimental data. Validation of the model will continue and refinements and updates will be incorporated as work progresses.
To develop an agenda on NEESgrid Data Curation and related issues, a Summit meeting was held in Chicago on March 18, 2004. Coordinated and sponsored by the NEESgrid System Integration team, the summit brought together experts in library information science, earthquake engineering, data infrastructure, and data curation, to forge a forward-looking plan needed to improve the NEESgrid data usage and curation. This report briefly summarizes the discussions in the meeting and outlines the data curation needs for NEESgrid.
The NEES NTCP API is a client side library used to write C programs that can interact with an NTCP server. The client API provides full functionality for each of the NTCP operations defined by the NTCP schema, as well as querying service data and receiving notifications on state changes.
v1.0, 05-06-2004 B. F. Spencer, Amr Elnashai, et. al.
This document describes in detail the scientific rationale for the MOST experiment, the infrastructure components that supported the MOST experiment, and the feedback from the community and the MOST team members about the experiment. Overall, the MOST experiment has been considered a success and many important lessons were learned.
This document explains the interactions between the NSDS, driver, and DAQ for the purposes of debugging, replacing the driver or DAQ code, or customizing the DAQ code. In addition to describing in detail the various components that constitute this system, the document also explains protocols and formats associated with data and control channels and data files, as well as error handling and syntax, and provides examples for each. Tools for testing components that have been debugged or replaced are also discussed. This document provides a minor correction to 1.2.
NEESgrid Project Timeline For Software Releases, Training, and Deployment - Short Version, describes/schedules all major tasks and events pending on the NSF sponsored NEESgrid development program. It can be used as an implementation planning guide for the deployment of the grid to earthquake equipment sites across the United States. This version was updated April 27, 2004.
v1.0, 04-24-2004 Laura Pearlman, Carl Kesselman, Sridhar Gullapalli, et. al.
This is a reprint of a paper that originally appeared in the 13th IEEE Symposium on High Performance Distributed Computing, June 2004. A writeup is also available from a symposium demonstration titled Showcasing the Features and Capabilities of NEESgrid: A Grid Based System for the Earthquake Engineering Domain by Sridhar Gullapalli, et. al.
Earthquake engineers have traditionally investigated the behavior of structures with either computational simulations or physical experiments. Recently, a new hybrid approach has been proposed that allows tests to be decomposed into independent substructures that can be located at different test facilities, tested separately, and integrated via a computational simulation. We describe a Grid-based architecture for performing such novel distributed hybrid computational/physical experiments. We discuss the requirements that underlie this extremely challenging application of Grid technologies, describe our architecture and implementation, and discuss our experiences with the application of this architecture within an unprecedented earthquake engineering test that coupled large-scale physical experiments in Illinois and Colorado with a computational simulation. Our results point to the remarkable impacts that Grid technologies can have on the practice of engineering, and also contribute to our understanding of how to build and deploy effective Grid applications.
This report describes in detail each step of the process of developing metadata about previously-performed tests and provides a roadmap of future metadata development. We will present a procedure to implement metadata generated about specifically-chosen tests of SAC steel projects. This report also introduces the NEESgrid Metadata Service (NMDS), which allows users to create, manage, retrieve, and modify metadata objects in a NEESgrid repository. Throughout the report we explain each step of the development process in detail.
This document consists of a presentation given at the April 23, 2003 NEESgrid developer training meeting. It consists of a walkthrough of the Example DAQ program, subroutine by subroutine, covering usage and notes.
This document provides answers to frequently-asked questions about NEESgrid's Data Acquisition system, which is currently implemented in the popular LabVIEW framework. Topics include data channel speed, limits, and decimation, calibration, hardware and platform recommendations, using a framework other than LabVIEW, and testing.
This document consists of a presentation given at the April 23, 2003 NEESgrid developers' training meeting that describes in illustrated detail the architecture of the NEESgrid Data Acquisition (DAQ) system and how it works. It provides an overview of the NSDS, driver, and DAQ.
The January 2004 NSF Site Visit team requested that the NEES System Integrator Awardee document the degree in which the NEESgrid System Acceptance Test Plan covers the requirements documented in the NEESgrid Requirements Traceability Matrix. This document summarizes the requirements coverage and details areas in which coverage is not complete.
This document is intended as a brief introduction to the components and capabilities of the NEESgrid and a roadmap for setting up a fully operational NEESgrid node using software release 2.2. Section 1 describes briefly each of the NEESgrid components and provides links to relevant documentation. Section 2 provides an overview of the steps necessary for bringing a NEESgrid node online. Section 3 briefly describes two standard experiments based on the Multi-Site Online Simulation Test (MOST) in July 2003 that demonstrate the various NEESgrid capabilities; these examples can be used for reference implementation and training purposes.
This document describes the NEESgrid Reference Implementation, two standard NEESbased experiments which demonstrate the capabilities of the NEES system. This guide will provide an overview of the NEES system, a discussion of the two standard experiments distributed with the NEESgrid software, and an explanation of how to get these experiments up and running.
Instructions and download links for the NEESgrid 2.2 components are included.
Installation instructions and guides for installing NEESgrid Release 2.2. API, installation, and reference documentation are also available.
This document describes the C language interface for the NTCP Control Plugin described in the Control Plugin Description (DRAFT). The audience of this document are people who are interested in implementing native c-language control plugins for the NTCP server. This document describes the general requirements of a plugin, the functions which must be implemented by a plugin, and the API available for the plugin to interact with the NEES server.
This document describes an example C language plugin for the NEESgrid NTCP server. This plugin will accept and execute any transaction proposal, with executing running for 30 seconds. Executing transactions may be cancelled by a NTCP client if desired. The purpose of this sample plugin is to show how to implement a plugin which accesses control point data and processes the various plugin requests as well as show how to compile a plugin module on linux and windows.
There are many existing data modeling techniques and tools that are available to help design and structure the data. Within NEES community, there have been some ongoing works to develop data dictionary and data models. The purpose of this document is not to provide an exhaustive review on the works related to data modeling but to briefly review and evaluate some of the relevant approaches. A brief summary provides a discussion on the approach currently undertaken to develop a project data model for NEES experimentations.
The Requirements Traceability Matrix is a representation of user requirements aligned against system functionality. It is used to ensure that all requirements are being met by the system deliverables.
This version of the Acceptance Plan lays out the system requirements, the components that are to be delivered, and the procedures for how those components will be evaluated for acceptance. Detailed information on test procedures will be added as appendices. It also demonstrates how the specific functionality criteria to be tested will be derived from the general text of the System Overview document. It is hoped that the formalization of an Acceptance Test Plan and Procedures will help ensure the delivery of an excellent software system that contributes to the success of the Consortium and of the NEES program in general.
The Multi-Site Online Simulation Test (MOST) took place on July 30, 2003. The MOST Experiment describes in detail the NEESgrid components, the experimental setup, the process of preparing and conducting the experiment, media and public relations activities, and feedback from the community and MOST team members about the experiment.
Instructions and download links for the NEESgrid 2.1 components are included.
Installation instructions and guides for installing NEESgrid Release 2.0. API, installation, and reference documentation are also available.
Instructions and download links for the NEESgrid 2.0 components are included.
NEESgrid Technical Report 2003-19: NFMS Reference Manual -- Release 2.0 is a developer's guide to the 2.0 release of NEESgrid File Management Service which describes classes, constructors, methods, and constants.
NEESgrid Technical Report 2003-18: NFMS User Guide describes the 2.0 release of NEESgrid File Management Service (NFMS).
NEESgrid Technical Report 2003-21: NMDS User Guide describes the NMDS API as of NEESgrid release 2.0.
NEESgrid Technical Report 2003-20: NtcpHelper Reference provides descriptions of all NtcpHelper functions and example syntax, as well as functions and syntax of other classes related to NtcpHelper.
The Project Execution Plan (PEP) presents the top level technical, cost, and schedule baselines and project management for the "NEESgrid: A Distributed Virtual Laboratory for Advanced Earthquake Experimentation and Simulation," project, submitted in accordance with National Science Foundation (NSF) proposal CMS-0117853.
NEESgrid Technical Report 2003-17 describes and assesses the synchronized video component of a NEESgrid-enabled experimental setup at Oregon State University.
The NEESgrid Teleoperations Control Protocol (NTCP) is used to perform remote control of physical experiments or simulations. An NTCP control plugin is a java class that implements the interface described in this document to communicate with a control system (or simulated control system). This document describes the current NCSA implementation of the NTCP control plugin, including methods defined in the NTCP control plugin interface, object types passed in as arguments to the methods in the control plugin interface, and example servers that could be implemented using this plugin architecture.
This document defines the strategy, requirements, scope of responsibilities, and process for the collaboration between the NEESgrid System Integration (SI) team and an Equipment Site (ES) for the Experiment-based Deployment of NEESgrid. The requirements laid out herein define SI deployment team expectations for the ES with respect to hardware, software, project plans, project lead, and points of contact. The section describing the process will outline the steps both the SI and the ES must take to properly coordinate this activity. The scope of responsibilities for the ES and the SI team and the tasks for each team are clearly stated.
This document is obsolete and has been superceded by System Acceptance Test Plan v1.0.
This report describes the architecture and specifies the protocols for proposing and executing remote control operations through the NEES Teleoperation Control Protocol. NTCP is particularly useful for multi-site distributed experiments which combine both computational and physical simulations. The document describes how the NTCP server and protocol perform in the context of the experimental framework and details how the NTCP server interacts with the coordinating simulation (or other client) during each of the three phases enacted during each timestep of the simulation; what kinds of information is maintained by the NTCP server, and the various requests that comprise the NTCP protocol. Security considerations and issues are discussed, as are future modifications and improvements. Finally, two appendices explain A.) how a community scheduler using the SNAP protocol could be used with NTCP to manage NEES resources and B.) give the full WSDL description of NTCP.
This document explains the interactions between the NSDS, driver, and DAQ for the purposes of debugging, replacing the driver or DAQ code, or customizing the DAQ code. In addition to describing in detail the various components that constitute this system, the document also explains protocols and formats associated with data and control channels and data files, as well as error handling and syntax, and provides examples for each. Tools for testing components that have been debugged or replaced are also discussed. This document provides a minor correction to 1.1, which in turn superseded NEESgrid Technical Report 2003-04, version 1.0.
This document explains the interactions between the NSDS, driver, and DAQ for the purposes of debugging, replacing the driver or DAQ code, or customizing the DAQ code. In addition to describing in detail the various components that constitute this system, the document also explains protocols and formats associated with data and control channels and data files, as well as error handling and syntax, and provides examples for each. Tools for testing components that have been debugged or replaced are also discussed. This document supersedes NEESgrid Technical Report 2003-04, version 1.0.
The NEESML Reference User Guide provides a comprehensive reference manual for the NEESML language, which is used to populate a NEESgrid metadata repository with objects and definitions of object types. The User Guide specifies the syntax for NEESML documents, describes the meaning of every NEESML construct, and explains how NEESML may be extended. A glossary of NEESML-specific terms is included.
This is a draft version of the NSDS system architecture document. It provides detailed component descriptions in list form for the NSDS web service interface and the driver interface/API. It also describes the NSDS defaults.
This document is obsolete and has been superceded by Requirements Traceability Matrix (TR 2003-13) v1.1.
This document presents the Requirements Traceability Matrix created by the User Requirement team and the methodology used to generate it. The Requirements Traceability Matrix is a representation of user requirements aligned against system functionality. It is used to ensure that all requirements are being met by the system deliverables.
NEESML is an XML format for defining NEES metadata schemas and uploading metadata objects into the NEES metadata repository. NEESML provides a syntax for defining object types, object attributes, and relationships between object types, including inheritance. It also provides a means for creating instances of object types, including the ability to link objects together in a variety of ways. The purpose of the type definition and instantiation mechanisms is to allow users to describe real-world objects of interest to them in order to enable browsing and retrieval of data and information within and across sites. This paper describes NEESML and gives examples of its use, but does not include a comprehensive reference for the format.
The set of documents provide instructions to install and configure the neesgrid 1.1 release software. The instructions cover software to be installed in the NEESpop, DAQ and TPM (tele-presence machine) systems.
The NEES Metadata Service (NMDS) provides applications with the ability to create, manage, link, and discover metadata objects in the NEES repository. This study investigates the performance of the current development version of the NEES repository implementation and discusses how the results impact how the repository implementation should be used and further developed.
In a follow-up to the April 2003 Equipment Site teleconference, the ES PIs discussed the need to devote significant time at the Awardees meeting to interaction among the SI and ES. The purpose of this document is to address issues and concerns presented by the ES sites, and provide clarifications as required. Dan Reed has developed a synopsis of this document in a slide show format for presentation at the NEES Awardees Meeting, May 23, 2003, in Park City, Utah.
The issues addressed by the SI team in this document fall into three major categories: establishing important and mutually satisfactory timelines and schedules for completion of milestones and deliverables; improving user support via a broad spectrum of communication venues, hands-on training, and improved documentation and accessibility to online resources; and providing responses to specific hardware-, software-, and networking-related questions and issues raised by the ES sites.
This document describes the system architecture for the NEESgrid project, the system integration element of the George E. Brown, Jr, Network for Earthquake Engineering Simulation (NEES). The result of NEESgrid will be a collaboratory, or "laboratory without walls," for earthquake engineering research. As illustrated in Figure 1, the NEESgrid collaboratory will link the national earthquake engineering community with up to twenty laboratories (see Figure 2), allowing teleoperation and teleobservation of experimental apparatus via the Internet (collectively, "telepresence"), access to data produced by these apparatus, and hybrid operations integrating physical and numerical simulations.
When completed, the NEESgrid collaboratory will enable four core capabilities. First, the collaboratory will link scientists to facilities to allow remote operation and observation of experimental equipment. Second, the collaboratory will link scientists to data to allow remote, shared viewing of real-time and archival data. Third, the collaboratory will link facilities with data, not only in the form of data repositories but also in the form of output from numerical simulations joined to physical simulations. Finally, the collaboratory will link scientists with other scientists, independent of time and location, to allow joint editing of documents, joint viewing of data visualizations, and joint operation and observation of physical and numerical simulations.
The NEESgrid Streaming Data Service (NSDS) will provide a common protocol for use by remote applications to receive streaming data from a running experiment over NEESgrid. This document defines requirements for the NSDS protocols, including communications between the NSDS server and its clients (requests, NSDP data) and communications between the NSDS and local DAQs. It also describes in detail the architecture and a possible implementation of an NSDS server and its modules. A section on the NEESgrid Telepresence Referral Service (NTRS) describes the NTRS server and the NTRS protocol.
This report describes the architecture and protocols for proposing and executing remote control operations through the NEES Teleoperation Control Protocol.
This document is obsolete and has been superceded by NTCP Control Plugin (TR 2003-16) v0.1.
This document describes the overall software design of an NTCP server (as described in [the ntcp protocol document]), using plugins to implement local policy and to performcontrol operations.
The purpose of this document is to provide a single source of information about hardware requirements for the major NEESGrid site resources. This document describes requirements for 4 stand-alone systems for supporting NEESpop, Tele-presence, Data Acquisition, and Local Data Storage capabilities. The need for stand-alone systems to support these capabilities depends on the requirements of each site. The NEESGrid software is developed and packaged by service category. Therefore, depending on the requirements of a site, multiple services could be hosted by a single system. The factors to be considered include the amount of data to be stored locally and the amount of video streaming to be done. If neither of these requirements is significant then a single system could host neespop, tele-presence, and local data storage capabilities.
This document describes further elaboration of core user requirements for the proposed NEESgrid collaboratory, or "laboratory without walls," for the George E. Brown, Jr. Network for Earthquake Engineering Simulation (NEES). This version should be read together with NEESgrid User Requirements, Version 2.0. When completed, the NEESgrid collaboratory will allow remote operation and observation of experimental equipment, visualization of real-time and archival data, and collaboration that is independent of time and location. This document extends understanding of core user requirements through data gathered from the NEESgrid User Requirements Workshop, held October 23-25, 2002 at the Timberline Lodge, Mt. Hood, OR. Specifically, a key request of workshop attendees was an annotated mock-up of the NEESgrid user environment. In addition, this document addresses concerns about technical requirements, about data usage, and about video latency. Finally, this document includes input from NEES Phase II equipment sites.
The purpose of this document is to provide a single source of information about hardware requirements for the major NEESGrid site resources. This document describes requirements for four stand-alone systems supporting NEESpop, Tele-presence, Data Acquisition, and Local Data Storage capabilities, respectively. However, the need for stand-alone systems to support these capabilities depends on the requirements of each site. The NEESGrid software is developed and packaged by service category. Therefore, depending on the requirements of a site, multiple services could be hosted by a single system. The factors to be considered include the amount of data to be stored locally and the amount of video streaming to be done. If neither of these requirements is significant, then a single system could host NEESpop, telepresence, and local data storage capabilities.
The integration and use of new technologies always involves risk. The goal of risk assessment and mitigation is to understand the risks inherent to an integration project and to develop strategies to effectively manage the project in a manner that mitigates the associated risks. The NEESgrid system integration project combines many information technologies that have previously not been used in support of engineering community collaboratories. Therefore, the project management effort includes specific activities for identification of project risks, and the development and execution of effective strategies for mitigating those risks. In addition, the NEES MREFC is the first distributed construction project undertaken by NSF, and the first undertaken by the Engineering Directorate of NSF. As a result, there are program risks associated with the novelty of this program that must be understood and included in any risk mitigation efforts undertaken by the NEESgrid project.
This Risk Assessment and Mitigation Plan is prepared as a component of the NEESgrid Technology Management activities, included as 4.4.3 in the Project Execution Plan (rev. March 3, 2003). Previous risk assessment documentation was included in the February 15, 2002 revision of the Project Execution Plan, and the tables provided in that analysis are updated in Section 4 of this document. The NEESgrid Risk Assessment and Mitigation Plan is maintained separately from the PEP, and is updated periodically to reflect changes in the risk profiles for project components.
This document has been superceeded by a revised Project Execution Plan dated 2003-09-22.
This PEP sets forth the organization, systems, and plan for managing the NEESgrid project that are in effect on February 28, 2003. This document is a revision of the PEP submitted on February 15, 2002, and accepted by NSF. The PEP for the overall NEES system integration component will be revised, as required, to incorporate lessons learned, changes in baselines (technical scope, cost, and schedule), and new project development and/or other arrangements among the participants. Revisions, as they are issued, will be acknowledged by all participants, and will supersede in their entirety previous versions. These project plan modifications will be administered via the change management practices presented in Section 8 of this document. These revisions will reflect new information on user requirements and experiences with implementing NEESgrid technical strategies. Such new information will assist the project participants in determining the order in which to undertake the development and deployment efforts in the plan, managing risk, and ensuring that the integration effort meets its objectives and deliverable schedule.
This document provides an overview of the software components under development within the NEESgrid Systems Integration Project. The particular decomposition of NEESgrid presented here illustrates the technical scope of the NEESgrid system to stakeholders in the NEES program. This document provides a high-level introduction to NEESgrid's various components and capabilities, so that stakeholders can learn about system components that will be delivered on or before Oct 1, 2004.
This white paper discusses issues of video synchronization as they apply to telepresence and data as data. NEESgrid uses AXIS video cameras, which allows users to manipulate their view of a remote experiment via the Internet. Issues involved in creating telepresence are discussed, including cost, hardware limitations, picture quality, and data format. Issues surrounding the production of streaming data suitable for analysis are also discussed, including the role of metadata and the hardware required. Finally, a deployment solution is proposed which explains how the same equipment may be used for telepresence and the production of data-quality video.
This document is to assist you in building and installing the NEESgrid NSDS driver for LabVIEW-based data acquisition systems. It covers compilation and installation.
This document is intended for NEESgrid sites wishing to install the supplied code for data acquisition (DAQ) and data handling. It covers getting the code, installation, testing and some ideas for site customization.
This document is for people wishing to understand the NSDS-driver-DAQ interactions, either for debugging or in the interest of replacing the driver or DAQ code. Sites customizing the DAQ code should also find this of use. Other documentation is planned for those incorporating this code into their sites.
This document describes the design for integrating support for the grid into CHEF [www.chefproject.org]. CHEF is a set of collaborative tools which are built on top of the Jakarta Jetspeed portal toolkit. The goal of this effort is to allow additional grid-oriented tools to be quickly built in CHEF which make use of grid services and operate within a grid security context. The initial purpose of this effort was to provide a framework to develop a collaborative portal [www.neesgrid.org] for structural engineers which uses the grid as its authentication.
NEESgrid is the systems integration component of the NEES Collaboratory. The NEES equipment sites provide state-of-the art physical testing capabilities to the earthquake engineering community. NEESgrid enables easy, remote tele-presence access and use of those advanced facilities. It also provides data management and analysis tools for investigators, and a curated repository as a publishing mechanism for investigators designed to make it easier for future researchers to understand and use the results from the studies. NEESgrid provides access to numerical simulation software and sample output to help facilitate the use of simulation modeling in earthquake engineering. Finally, it is based in a collaborative framework built upon the concept of team-oriented research, where members share ideas and information to improve the outcome of the project. The complete NEES Collaboratory is a powerful set of information technology, numerical, and physical simulation resources intended to facilitate a revolution earthquake engineering research and practice. NEESgrid provides the scalable and extensible information technologies and services to enable the Collaboratory, now and in the future.
The System Integration Team has interacted with the NEES community over many months to better understand user requirements, and to incorporate these requirements into its system architecture specification and project plan. Between now and 2004, the Team will be demonstrating the capabilities of NEESgrid at various earthquake engineering conferences and workshops, and working prototypes will be posted for use on the project website (www.neesgrid.org). A key milestone in the integration of the system is a full system prototype demonstration that will be conducted in July of 2003. New features of individual components are scheduled for demonstration approximately every 3 months beginning in April 2003.
This document provides an overview of the features of NEESgrid in the context of how each feature can facilitate or enhance collaborative earthquake engineering research and practice once the NEES Collaboratory becomes operational on October 1, 2004. The document is structured to follow a stepwise approach to experimental research, discussing the specific NEESgrid features or capabilities being provided to support each step in the process. For each section, pointers to additional information resources are given that can provide details concerning any aspect of the system or its features. Readers are encouraged to use these information resources to satisfy their individual levels of interest in each topic.
The NEESgrid curated data repository requires high-volume, high-throughput, reliable, secure storage technology that can provide ready access to heterogeneous data ranging from highly structured metadata to relatively opaque formats such as digital video. In addition, the technology needs to be mature and flexible enough that data can be preserved even when storage technology and data practices inevitably evolve. A number of storage and access technologies exist that meet some of these requirements, including commercial database management systems, standard data and metadata formats, standard data exchange protocols, network file systems, digital library technologies, and storage brokers. However none of these technologies by itself meets all of NEESgrid's requirements, so an appropriate combination of them should be employed. In the end, it is our opinion that maturity and flexibility are by far the most important requirements, since by meeting them we can minimize the risk that the storage technology will become obsolete and therefore necessitate extensive re-implementation of the repository. NEESgrid is also a distributed system. Although the curated data repository will be centrally located in order to take advantage of economies of scale and favorable network location, it will still need to interoperate with local storage mechanisms at the sites. For this reason, the technologies used should require as little specialized expertise as possible to maintain. Otherwise, there is a risk that sites will have difficulty moving their data to and from the repository, and that new sites will find it difficult or costly to join NEESgrid.
The NEESgrid Metadata Service provides access to metadata about a variety of entities, such as experiments, researchers, apparatus, events, and facilities. The service is designed to allow remote clients to browse, update, and otherwise manage metadata objects representing these entities of interest. The metadata objects are represented in a simple, consistent manner, which allows them not only to contain attributes of various types, but also to make reference to other objects. The objects are also tracked through aversioning system and protected through access control and object-level locking. Using the metadata service, remote clients can retrieve full or partial information about objects, request uploads and downloads of data files to and from the repository, and make full or partial updates to objects.
The NEESgrid Data and Metadata Harvesting service will provide NEES users with the ability to transfer data and metadata to the central repository. It will also enable users to manage the data and metadata in a variety of ways, including organizing data and metadata objects into projects, updating and removing data and metadata objects, and controlling who has access to the objects.
05-12-2002 Sridhar Gullapalli, Carl Kesselman, et al.
This document lays out a roadmap for the planned development and early adoption phase of the NEESgrid project. It covers the period from April 1 to October 1, 2002. The results of these efforts will be the deployment of an early NEESgrid infrastructure with limited functionalities, with a view to demonstrate an initial set of capabilities.
A PowerPoint slide presentation, given at COSMOS, which explains the need for a NEESgrid data repository and proposes a process for undertaking the construction of one.
Advances in data volume associated with sensor and data acquisition technology and the increased complexity and value of model test data make it clear that there is a real need to implement better, flexible, and more general standards for archiving data. The new standards should make it easy to create, edit, share, query, and search through databases and they should facilitate comparison of numerical simulations with experimental data. This paper presents a strawman data structure for physical model test results; perhaps a similar structure would be useful for numerical simulation results. It is anticipated that that this structure will be used to establish a Model Test Markup Language (MTML). XML (eXtensible Markup Language) provides an ideal syntax for MTML. The goal of this paper is to stimulate convergence toward an accepted structure of metadata.
No single technology will address all the requirements for integrating a scientific data repository into a collaborative experimental framework, and IT and domain specialists must collaborate in developing such a repository. This PowerPoint slide presentation, given at COSMOS, which discusses in detail possible technology strategies and examines their advantages and disadvantages. Technologies which might be useful for the integration of scientific data collections include XML and XML schema, XLink and URI, SOAP, XSL, RDF, and Semantic Web. The presentation also discusses possible architectural schemes for integration of data repositories, including federation and harvesting; and the issue of indexing and access.
This document is intended to define some common imaging terminology and related consequences of image processing and manipulation which are associated with data that might be collected by a NEESgrid site. This document is intended as a living document and will be updated as needed as an archive of information relative to the NEESgrid project. It is not a comprehensive review of imaging but rather a collection of salient points as they relate to imaging issues associated with NEESgrid. Much of the information herein is compiled from various sources on the WWW which will be documented in the references.
This document is intended to assist NEES Equipment Sites (ES) in understanding the functionality of the NEESgrid TelePresence Mode, and also to aid in establishing a budget estimate necessary to procure a uniform set of resources to support the NEESgrid TelePresence Environment. It should be read in conjunction with the NEES Scoping Study1, NEES-POP 2 and the NEES LAN3 documents and seeks to outline specific hardware and software which supports the current configuration for NEESgrid TelePresence Mode as currently implemented at the date of issue. It should be expected that the hardware and software described herein will evolve as the NEESgrid project development continues, thus changes in the configurations described are to be expected. Evolution of the system architecture, which will occur during the course of this project, means that some of the components specified in early versions of this document may become superceeded or obsolete. Every attempt will be made to retain compatibility, to the maximum extent possible, with the recommendations of previous versions of this document. It is intended that this document also provides sufficient information for a NEES Equipment Site to develop their own procurement scenerios for TelePresence resources. Before an actual procurement is executed, it is recommended that an Equipment Site contact the System Integrator to confirm that the latest recommendations are in hand.
This document is intended to help NEES equipment sites to ensure that they have sufficient network and computing equipment and personnel to support NEESgrid services. This is a requirements document, and does not recommend specific hardware or software.
This document is obsolete and has been superceded by NTCP 2003-07 v0.4.
The purpose of the NEESgrid TeleOperations Protocol (NTOP) service is to provide a common protocol that can be used by remote applications to interact with a running experiment over NEESgrid.
v1.0, 02-15-2002 Carl Kesselman, Randy Butler, et al.
This document is obsolete and has been superceded by System Architecture v1.1.
The Community Requirements Workshop Final Report (Technical Report 2001-03) summarizes the data collected from the site visits and surveys, and information gained during the workshop itself. It is a first step in bringing the EER and IT communities together to help define a useful approach to building a national NEES collaboratory to transform the way the earthquake engineering community works.
In this report, we describe the function that the NEES-POP is intended to fulfill, outline its planned hardware and software configuration, explain how we expect a NEES-POP to function at a site, and present our plans for development and deployment. The report does not provide complete specifications for hardware or software (these will be provided in later documents), but we believe does provide enough information to allow critical review.
02-14-2001 Tom Prudhomme, Carl Kesselman, et al.


Unfortunately, fear of age discrimination in hiring decisions isn't just paranoia. Read on to understand why ageism occurs and how to combat its effects.
If your career is more than 15 or 20 years old, you may have wondered about the subtle—or not-so-subtle—influence of age discrimination in job searching and recruiting.
So is concern about ageism paranoia or smart strategy?
According to Jim Niemela, founder and president of ZimZee Recruiting, age discrimination in recruiting and promotions is real. Unfortunately, recruiters and hiring managers—consciously or subconsciously—tend to devalue job candidates based on an impression of advanced age.
If that doesn't sound creepily Orwellian enough, Jim adds that ageism is a moving target depending on your industry niche. For example, he explains, a 50-year-old software developer might not feel the effects of ageism, but a 50-year-old software sales rep just might.
The good news is that there are a few simple, effective ways to combat age discrimination in your resume.
First, operate on a need-to-know basis.
A resume must be completely honest, but it isn't a full-disclosure document. When it comes to age, what they don't know can't hurt you. You're not required to include information that indicates your age and thereby may generate an unfavorable first impression.
Don't list the year you graduated from college.
Don't list dates on jobs that are more than 15 years old.
Remove any outdated information that might date you. For example, don't list proficiency in WordPerfect.
To be completely honest, these strategies are mildly annoying to hiring managers—they want to know how old you are. They also might want to know your past salary and your marital status, not to mention your golf handicap, where you stand on BYU versus UofU, and all kinds of other tidbits that are none of their business and may be illegal for them to inquire about.
The purpose of a resume is to get an interview. Feel free to decline to provide information that divulges your age and may generate discrimination.
But say your age-scrubbed resume lands you an interview. How do you combat ageism in a face-to-face interview?
It's clear that ageism is unfair and often an unhelpful measure of a job candidate's value. But let's dig a little deeper to understand why age can affect hiring decisions.
What are hiring managers afraid of when they see an older candidate?
Hiring managers are looking for energetic and sharp candidates who bring cutting-edge expertise, who are flexible and adaptable, who are driven to succeed, and who know how to relate to today's clients in today's marketplace.
Hiring managers fear that older candidates may be set in their ways, out of touch, technologically behind, and low-energy.
So if age discrimination is an issue for you (and even if it isn't!), consider finding ways to let potential employers know that you're ready for a challenge, determined to catalyze results, and current in your field.
Before the interview, research your target company and gain some expertise in their branding, market niche, and growth strategy. When you arrive at the interview, dress sharp and walk into the room with a twinkle in your eye and a spring in your step.


Make an elegant statement with these unique Glitter Rose Tapers. Simply exquisite in any decor or as a gift for someone special.
Made of pure beeswax in your choice of natural or hand-dyed colors, adorned with your choice of silver or gold wax paint & glitter edging. Handmade to order, no two candles look exactly the same.
This listing is for your choice of one set of 3 or 4 Glitter Rose Tapers, approx 10" tall.
Photos show examples in assorted colors and sizes from previous orders.
Yours will be handmade to order in 10" height, in the colors & quantity of your choice.
Please note: I hand-dye the beeswax in small batches, color shades vary slightly each time.
• SIZE: approx 10" x 7/8"
In my signature packaging: depending on number of tapers ordered - kozo hemp lace paper or a white gift box, tied with tulle ribbon. A Forest Candle Studio mini note card is enclosed (candle info & burning instructions are on the back).
See the "Shipping & Policies" tab for PAYMENT & CURRENT ESTIMATED SHIP DATE for this item, and my general SHOP POLICIES.