text:
Indigenous Peoples of the Americas
Search results
Papers of John Clum
John P. Clum was the Indian agent at the San Carlos Indian Reservation, 1874-1877; later newspaper editor, postmaster, and mayor of Tombstone, Ariz., as well as postal inspector and lecturer in Alaska. His son, Woodworth Clum, was a newspaper editor of ...
castanoe - 2014-03-09 13:13
Papers of Leighton Finley
Finley was a U.S. Army officer, Lieutenant, 10th cavalry, in Texas, 1880-1881, Fort Leavenworth, Kansas, 1881-1884, and Arizona, 1885-1892. Collection includes a diary, notebooks, biographical material, and photographs relating to Finley's Army ...
castanoe - 2014-03-10 13:58
Papers of Gertrude Edna Lewis Gates
Gertrude Edna Lewis Gates was an Arizona rancher; operated the DA Ranch, 1910-1922, in Cornville, AZ, Yavapai County. Collection includes correspondence, notebooks, cattle records, and financial papers pertaining to the operation and maintenance of the D ...
castanoe - 2014-03-10 14:03
Journal of John Gregory Bourke
John gregory Bourke, 1846-1896, was a U.S. Army soldier, author, and ethnologist. The collection contains a holograph journal, with sketches; kept by Bourke while a lieutenant in the U.S. Army, 3rd cavalry. Bourke describes visits to the Bannock Indians, ...
castanoe - 2015-11-05 10:53
Papers of the Oury Family
Correspondence, diary, photographs, deeds, articles and speeches chiefly relating to Arizona territorial military experiences of Oury family members. ...
castanoe - 2014-07-31 09:22
Papers of Louis Rosenbaum
Louis Rosenbaum was a merchant from New Mexico. This collection cosists of letters and power of attorney, from Las Cruces, N.M., Sept. 6, 1877. Letter to John B. Morrill requesting he act as Rosenbaum's agent at the San Carlos Indian Reservation, ...
castanoe - 2015-12-21 10:43
Papers of John J. Wingar
John J. Wingar, 1833-1907, was a Methodist clergyman and Arizona pioneer. Wingar moved to Prescott in 1877, and later lived in Florence, Pinal, Globe, and Tempe. He was active in establishing a school at the San Carlos Apache Indian Reservation. The ...
castanoe - 2016-01-05 16:28
The Story of Patchy
Typescript of unpublished manuscript, with photographs, concerning the story of Apache May, a young Apache girl found in May, 1896, by Cochise County cattleman and former sheriff, John Slaughter, in an abandoned Apache camp. She lived with the Slaughters ...
castanoe - 2016-01-13 08:53
Record of William Henry Corbusier, Colonel, U.S. Army Retired
Typescript of biographical account and reminiscences about events at posts while serving as surgeon,1872-1875, and 1884-1888. Includes information about the health conditions of Native Americans and soldiers at the Verde River Indian Agency, San Carlos ...
castanoe - 2016-01-20 09:13
The Navajos and the Indian Bureau
John Henry Holst was the Supervisor of Indian Education, U.S. Dept. of the Interior, 1928- 1943. Original typescript with holograph corrections, written about 1950, chiefly concerning education on the Navajo Indian Reservation during the 1930s and early ...
castanoe - 2016-01-20 09:51


text:
Politicians and Election, Vote in Freedom, Actively Participate in Democracy, Vote for Change, Online referendum
Sharad Pawar
> India > Politicians > Nationalist Congress Party > Sharad Pawar
Sharad Pawar is ready for your opinion, support and vote. Vote online NOW!
Sharad Pawar - for
शरद गोविंदराव पवार | An Indian politician. The current president of the Nationalist Congress Party (NCP).
Sharad Pawar - against
Click, if you do not support Sharad Pawar. Say why.
बाळासाहेब ठाकरे maharashatra eiection 1996, sharad email, na.sharad pawar, sarad pavar, शरद पवार यांनी and more...
Related polls > Sonia Gandhi, Atal Bihari Vajpayee, Narendra Modi, Manmohan Singh, Jawaharlal Nehru, Rajiv Gandhi, Pratibha Patil, Indira Gandhi, Anna Hazare, A. P. J. Abdul Kalam, Jayalalithaa Jayaram, Abhishek Singhvi, Aruna Roy, Lalu Prasad Yadav, Nara Chandrababu Naidu, Y. S. Rajasekhara Reddy, Mayawati Kumari, Rajnath Singh, Mamata Banerjee, Rajendra Prasad, (Sharad Pawar) and more...

subset: commoncrawl


text:
I love historical movies, books and plays. The trouble is that many historical stories are too long because so much has to be explained. In the new play at the Lillian Theatre, God's Gypsy, directed by Joel Daavid, about Teresa of Avila, this had a touch of excess length, but, in general, Coco Blignaut's adaptation of Barbara Mujica's NY Times bestselling novel, "Sister Theresa" flowed with humor and tension mixed with the facts of the day.
The play stars writer Coco Blignaut as Teresa, Tsulan Cooper (Sister Angelica,) Daniel DeWeldon (Father Braulio) and Edison Park (Father Javier.) The team of actors work shopped the play for over three years, perfecting the scenes. Also in the cast are David Haverty, Abbe Rowlins, Pat Satcher, Carole Weyers, and Jeanne Witczak.
According to Mujica, Coco looks very much like the saint, herself, and seem to fit into the blessed role quite easily, but the dialogue, at times, was a bit stilted.
Before she was a popular saint, Teresa of Avila (known in the Spanish countries as Teresa de Jesus) was very much a woman and God's Gypsy gives a bold, sexy, humanizing portrait of this 16th century mystic who became a controversial reformer of the Catholic Church. Growing up spoiled as a morrano (secret Jew), she was sent to a convent to learn discipline and instead found a religious fervor. Through the sister's writings, we learn of her own personal relationship with God, one that did not rely on the priests to interpret and her many visions.
Called a 'saint for our age", Teresa believed that an immediate and direct connection with God could be had through meditation. Many of her thoughts might have come from her Jewish ancestry since this idea is prominent among Hebrew philosophy. The Spanish Inquisition, however, had a difficult time accepting this modern concept and several times called Teresa in for questioning accusing her of blasphemy, heresy, and demonic possession.
Celebrated violinist Lili Haydn contributed her own original score and played at select performances.
The realistic set design was done by director Joel Daavid, with lighting by Leigh Allen, sound by Christopher Moscatiello, and costume by Michael Mullen. The play, itself, was produced by Mike Abramson.
I recommend the play not only for the education it provides, but for the superb acting skills seen.
Tickets cost $30 and reservations can be made going to God's Gypsy or calling 866-811-4111. The Lilian Theatre is one and a half block west of Vine at Santa Monica Blvd. (1076 Lillian Way, Hollywood 90038.) The play runs through January 12, 2014 and performances at Thursdays, Fridays and Saturdays at 8 pm and Sundays at 6 pm. The theatre will be dark Dec 26-29.


text:
Needles Necklaces
As the brainchild of Japanese design veteran Keizo Shimizu, clothing label Needles connotes a highly referential yet ultimately singular vision of menswear. Operating as Tokyo's best-kept-secret before infiltrating New York City via the Shimizu-helmed Nephethens store, the brand freely integrates style cues from both cultures in equal measure. Shimizu's early-life affinity for Ivy-league deadstock translates into off-kilter collegiate pieces, which are injected with a welcomed sense of unfamiliarity. Given his background at Nephethens, Shimizu approaches design from a retailer's viewpoint, assembling collections that touch on a variety of styles while maintaining an air of calcultated curation. This stylistic patchwork gives way to multi-textile constructions that defy the rigidity of retrograde American menswear, offering an unexpected warmth to Needles' cross-cultural collage.
There are currently no products available for Needles Necklaces.
Please select another designer or sign up below to receive email updates on new product arrivals, special offers and exclusive events.


text:
nitros brauchte ein neues Logo Design und hat einen Wettbewerb auf 99designs gestartet.
Aus 115 Designs von 36 Designern wurde eine Gewinner gewählt.
Looking for a brand new logo for GetYourMeal.com website. Business is based on a revolutionary concept, expecting the logo to match the business. Logo should be elegant and contemporary. Since the brand is 3 words combined, use your creativity to distinguish "your". We prefer all in small case unless you think you can do better capitalizing the initials.
We may not use any tag line but a compelling tag line will be appreciated and may earn more business from us.
We are looking for a brand new logo. Please submit your design in normal (white background) and reverse format (using any warm color background). Please see what I want and don't want section. Logo should be in a vector format like that produced by
Adobe Photoshop or Adobe Illustrator. We also want the final delivery of the logo to include "Logo Beta" and "Logo".
We are a startup eCommerce company schedule to launch our service in Feb, 2009 in Charlotte, NC and eventually go nationwide. We received several logos from different firms but so far, we are not satisfied. the logo on our website is a placeholder and the design of our current website GetYourMeal.com is a brochure website and should not be considered as to our liking.
GetYourMeal.com is a location based service that showcases food items/menus of participating restaurants and have them delivered to customers using a network of members to our website. Every menu item is categorized, tagged and customers browse the restaurants/meals around their location. Customers pay for delivery which is based on the distance of the restaurant from the customer. A member of our website gets to deliver the order once prepared by the restaurant and earns all the delivery fees + tips. Take away and dine-in option are also available. We crowd source the delivery part of the order.
Please note, we do not manufacture any products. We are strictly a service provider with a platform for restaurants to post their menu online, customer to browse and purchase, and delivery drivers (member) to deliver the orders and earn delivery fees + tips from our system.
Feel free to call in case of doubt: 704-900-3126
- Muted or Bold colors
- Warm color like Orange
- Light or Dark Green
- Red and Blue optional
- Simple and contemporary
- Color blending on logos
- GetYourMeal word is long, do not want any pictures on either side- Any picture/art of a waiter, car, driver, running man or waiter holding a tray.
- Picture of food, fruit, meal, burger or vegetables. We do not manufacture any product.
- Samples of bad logo
- Any kind of extra art/image in between getyourmeal that elongates the logo more.
Finden Sie heraus, wie ein Designwettbewerb funktioniert, oder lernen Sie mehr über unsere Logo-Design-Angebote.


text:
hhedaya necesitaba un nuevo diseño de página web y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 75 diseños de 14 diseñadores freelance.
Avion Lending is a prestegious lender for high end private jets, turboprops, helicoptors and smaller airplanes. We offer a unique product in the aviation marketplace that seperates us from the competition. We offer loans without borrowers having to submit personal financial statements or obtain credit or income checks. Our loans are simply guaranteed by the value of the aircraft.
High end executives, management, high net worth indiciduals, airplane brokers, CEOs of large companies, business to business.
We are launching a contest for a cutting edge design that will wow the audience. Although we have provided wireframes supporting the elements we are looking for we are completely open to artistic license.
Home Page, Calculator/Apply Online page, Template page (wireframes attached (template ppage has logos for various manufacturers. We would also like these logos on the home page. Affiliation logos are also uploaded. maybe greyscale them to make them conform to the footer and look uniform.
several industry websires can be found at http://nafa.aero/directory.cfm?doLevel=2 , http://www.airfleetcapital.com/ratesandterms.asp , we are not crazy about any of the designs but you will get an idea of whats out there.


text:
When buying a car, it's tough to balance being informed and saving time. That's why we encourage you to use only the tools below that are most valuable to you. Each one provides information and steps to help streamline the process at the dealership.
Complete one of the steps below to begin saving time at the dealership Log In to Save Your Progress
saved at the dealership! Log In to Save Your Progress
saved at the dealership! Structure My Deal tools are complete — you're ready to visit Helena Ford Lincoln
Exterior Color: Magnetic
Vin Number: 1FMJU1JT3LEA08278
Stock: A08278
View this New Ford Expedition for sale in Helena, MT.
Skip paperwork! Save time at the dealership by doing the work from home!
Helena Ford Lincoln
3365 Hwy 12 E
Directions PO Box 4489
Helena, MT 59604
Quick Specs
Quick Specs
Quick Specs
Quick Specs


text:
cloudplaynetwork necesitaba un nuevo diseño de página web y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 56 diseños de 24 diseñadores freelance.
We are a media startup producing game apps that are played both online and off.
US TV gameshow fans, Online gaming fans, online social network users.
I want a clean main page based on the elements given. I want the site uncluttered, clean, but can still convey a feeling of fun.
The site should contain links to our various shows represented by the show logos provided.
About Us and FAQ links as well.
Attached is company name and logo - CloudPlayNetwork
Also attached are icons for 3 of the shows we produce. - TheRaceat8pm, WhoWantsat6pm, and Walktoat5am.
Play around with the icon and logo size.
Please provide space for future shows. Same icon, different name and colors.
Please play around with the initial treatments. I will give feedback asap to the design paths I want to take.
The links are to the respective shows main page. The designs of those will follow. For now, we stay on the main page.
I can have anything on the site animated, so please factor that in.


text: This advanced-level grammar course focuses on speaking and writing in academic contexts. Students learn to use English grammatical structures more accurately, meaningfully, and appropriately in their oral presentations and in their written work. Activities include writing and speaking production, text analysis, error identification, editing, grammatical consciousness-raising, and focused exercises. Two projects, each having speaking and writing components, are required.


text:
Obviously the most exciting movie news of the moment is the recent confirmation of Pitch Perfect's forthcoming sequel (sqee-quel). At the Rebecca Minkoff show on Friday during New York Fashion Week, Anna Kendrick said she's happy she doesn't have to keep this joyous news a secret (squee-cret) (last time, promise) anymore. "I haven't read the [script]," Kendrick told Cosmopolitan.com. "I think the concept musically might be a little bit different. Obviously we're going to be doing what the audience loved in the first one."
If it were Kendrick's pick? "Maybe some Beyoncé covers would be good," she said. "Maybe a little 'Partition'?"
Kendrick said she especially loved singing R&B in the first movie. "No Diggity was my favorite performance in the first one, so I hope we get to play around with that a little bit, even though we're probably not cool enough to!"
She also confirmed that the set of Pitch Perfect is basically the best place ever. "When I'm on the set of Pitch Perfect — and I'm sure it's going to happen again — everyone is singing all the time," she said. "So you end up signing in the grocery store, shopping, and you need to get it under control, it's not a cute look."
The Minkoff show was Kendrick's first this fashion week. "I was worried it was just going to be a lot of mean girls. But everyone is so welcoming," she said. "It's also so weird, it's, like, the models look really severe, and I keep catching eyes with them here, and I think they're trying to stop themselves from cracking up because obviously they're doing something a little bit strange. So, it's really like this kind of high-glamour concept, standing in front of a bunch of people showing off amazing clothes. But so obviously even though their job is to look really mean, they're probably really sweet, too."
Photo Credit: Shiona Turini


text:
Refine your search
Eastbourne Bandstand
Grand Parade,
Also at this Venue
The Bandstand is an iconic venue set in the heart of Eastbourne's Beautiful Seafront and is an ideal venue for your special day. With breathtaking views over the beach and out to sea it boasts unique 1930s architecture and an atmosphere all of its own.
The Bandstand is offered for hire for Weddings, Civil partnerships, naming days and renewal of vows around the existing event programming.
Your venue hire includes:
- 2 members of our staff to man the doors into the main arena (the downstairs section of the Bandstand)
- The free provision and staffing of a licensed bar inside.
- 600 chairs in the arena (the chair configuration cannot be altered)
- One table and up to 12 chairs on the stage for the ceremony itself
- One microphone attached to 2 speakers
- The playing of music from a central location if a cd is provided
Visit our website for latest hire costs.
- 0 people
- 0 event rooms
- 0 bedrooms
The Bandstand is situated on the seafront opposite Devonshire Place. Pay and display parking on the seafront seven days a week. Eastbourne railway station is just 10 mins walk.
with charge
: 1 mile from Eastbourne station
- Baby changing facilities
- Cash Point
- Coach parties accepted
- Credit cards accepted (no fee)
- Disabled toilets
- On-site light refreshments
- Public toilets
- Telephone (public)
- Welcome Host
- Accepts groups
Self-Assessed Accessibility Details
- Designated parking for guests with disabilities
- The surface of the car park and pathway leading to entrance:
- is solid
- The route from the parking area to the entrance:
- Has a ramp
Public Areas
- Level access (no steps/thresholds) or access by ramp or lift:
- From the entrance to reception / ticket area
- To a specially adapted public toilet suitable for wheelchair users
- To the gift shop
- Good contrast between the floor and walls
- Contrast markings on clear surfaces such as glass doors
- Baby changing facilities
- Visitor information available in large print (14pt and over)
- Entrance is well lit
- Hearing loop system
- Seating available for visitors with limited mobility
- Clear signage
- Effective lighting for visually impaired visitors
- Good colour/tonal contrast for visually impaired visitors
- Routes/pathways suitable for wheelchair users or visitors with limited mobility
- Displays at suitable height for wheelchair users / children
- Audible alarm system
- Visual alarm system


text:
Our items are always locally sourced when possible. By purchasing local goods, you are recycling money back into our local economy, helping to strengthen our community.
Our 2020 Season Runs April 4 Through November 21.
Saturdays 8am – 12pm
Welcome to Western NC's most premier farmers market! Since 1980, we have been providing Asheville and the surrounding area with a full range of local, sustainably produced produce, meats, eggs, cheeses, breads, plants, prepared foods and crafts. Day vendors complement the members' offerings with additional products and services. The North Asheville Tailgate Market is a weekly, Saturday morning gathering of the best farmers, craftsmen, and bakers. With over 40 vendors and more than 40,000 annual customers, the market's energetic and warm environment exemplifies the celebrated diversity of our community.


text:
Product Specifications
- Brand: MindWare.
- Item Number: 400100739525.
- Manufacturer Number: MW56161.
- Recommended for ages : 7 to 13+.
- Gender: Both.
-Shipping Estimate
|Canada Post
|Zip code is required
|Local Pickup at Kool & Child: Please allow 24 hours. Call if in a rush.
|Local Delivery to communities between Nanoose Bay and Victoria on Vancouver Island by courier: Nanoose to Victoria via Geazone courier


text: Seller: iconsgr (2,309) 96.3%, Location: Volos,Magnesia, Ships to: Worldwide, Item: 132088193730 Ancient Greek Bronze Museum Statue Replica Of Hermes Code: 1208 Dimensions: 14x6 cm 5.53x2.37 in Weight: 400gr Material: BRONZE Color: MUSEUM OXIDIGATITION This is a handmade Museum Statue Replica Of Hermes made in Greece, from 100% bronze using the traditional "lost wax" technique. This is the same technique used by the ancient Greeks to create bronze sculptures and arsenal. The prototype which it was made by is a museum exhibit. The museum color is given through the process of oxidization Description: Normal 0 false false false EN-US X-NONE X-NONE Shipping: Handling time may take up to 10 days because the item is made after it is purchased. Shape and size may vary up to 0,5 cm because it is a handmade product. Shipping takes from 7 (European countries) to 25 working days (rest of the world) . Please understand that the above is only the estimated delivery time, it may delay due to strike actions, severe weather, custom reasons or peak seasons, such as Christmas / New Year Holidays. Payments: We only accept payment with PayPal. 5***** star feedbacks are greatly appreciated. If for some reason you feel that you are unable to leave 5 star feedbacks please contact with me and we will try solving the issue. Please note: Import taxes and other charges are not included in the item price or shipping cost. Please check with your country's customs office to determine what or if there are additional costs prior to your purchase. Condition: Handmade - New, Material: Bronze


text:
It's been nearly three years since "Seinfeld" star Michael Richards' ugly meltdown in a comedy club when he became almost unrecognizable, consumed with anger as he spewed racial slurs – an image that's become no less cringe-worthy with time.
After battling his demons privately for the most part, Richards confronted them publically Sunday night with a gutsy, dangerous burst of comedy on "Curb Your Enthusiasm," which is nearing the end of a season-long storyline centering on a fictional "Seinfeld" reunion.
Like "Seinfeld," the silly and often-serpentine plots on "Curb" require a little explaining: Richards may have Groats Disease, which is distracting him from the reunion special. Larry David, who based a past "Curb" episode around the fictional affliction, tells him not to worry, and agrees to introduce Richards to Danny Duberstein, an acquaintance living with the disease.
When Larry learns Duberstein died two months earlier, he convinces his African-American houseguest, Leon (J.B. Smoove), to pose as the Jewish Groats victim and reassure Richards. The scheme backfires, and Richards loudly rips into Leon, dressed in a Louis Farrakhan-like outfit, outside the TV studio.
"If only there were a horrible name that I could call you that would make you as angry as I am!" he screams at Leon, after cursing him out and threatening him.
Richards then turns around to see a crowd of onlookers pulling out mini-video cameras – his real-life racist rant was captured on amateur video – and gives a cry of helpless, déjà vu-driven agony.
To be sure, a few laughs aren't going to make the stupidity and hurtful nature of Richards' 2006 disgrace disappear. But give him – and David – credit for confronting the elephant on the set.
In some respects, this confrontation was a classic Larry David moment. Much of his humor derives from his saying what people may be thinking – or least what he's thinking – during uncomfortable situations. He's also mined his life for material – no more so than this season, in a multi-meta fashion: his real-life divorce is apparent fodder for his "Curb" divorce, even as his "Seinfeld" stand-in George Costanza's divorce plays a key role in the "reunion" show.
If you have trouble keeping that straight, just imagine what the "Curb" actors go through improvising scenes around David's loose show outline. One wonders how much of Richards' tirade against Leon was scripted.
The "Curb" appearances have marked a comeback of sorts for Richards, who is known less these days as the wacky neighbor Kramer, and more as the comedian with anger issues. Of all the "Seinfeld" cast members, he has the most to gain or lose by participating in the fictional reunion, which will play out in this Sunday's finale.
He may be a long way from redemption, but Richards is at least next-door to making us laugh again – even if it's at him, rather than with him.
U.S. & World
Hester is founding director of the award-winning, multi-media NYCity News Service at the City University of New York Graduate School of Journalism. He is the former City Editor of the New York Daily News, where he started as a reporter in 1992. Follow him on Twitter.


text:
Covid-19 | Deliveries are guaranteed (see conditions by country). Wines will be stored FOR FREE in our warehouses.
Meursault 1er Cru Genevrières Latour-Giraud 2009
Cuvée Belle Epoque Perrier Jouët 2006
Domaine des Lambrays is located on the Côte de Nuits in Morey Saint-Denis. It was bought by the LVMH group in 2014. It owes its name to the famous Grand Cru Clos des Lambrays which it owns as a virtual monopole. Besides the Clos des Lambray, the domaine produces stunning Morey-Saint-Denis as well as white wines in Puligny-Montrachet, bringing the total area of the vineyard to 11 hectares. Yield is low (28hl / ha), harvests are done by hand and aging takes places over eighteen months in 50% new oak barriques. The entire range is exceptional. In comparison with the Burgundian elite, prices remain reasonable. But the domaine's reputation continues to grow worldwide.
Clos des Lambrays is one of the five Grand Crus of the commune of Morey-Saint-Denis, and produces wines that are probably the most typical. Domaine des Lambrays owns almost all of Clos des Lambrays, only a very small part belongs to Domaine Taupenot-Merme. Full-bodied, concentrated and remarkably elegant, the Clos des Lambrays has a rare and complex aroma: notes of blackberry, blueberry and raspberry, and as it ages, undertones of truffle, spices, liquorice, violet and undergrowth. Its ageing potential is generally above 20 years.
Free and unlimited data access to 60,000 price estimates
Current price estimate 1990
Auction historyClos des Lambrays Grand Cru Domaine des Lambrays 1990
Do you own this wine?
Current trend of price estimate
Tasting notes
General :The «bio» designation covers certified wines produced by biodynamic or organic methods, sustainably produced wines, and «environmentally friendly» wines that are not officially certified.These designations apply to recent vintages (the date of certification, if known, is specified in the estate description).See the blog article for more information on this designation.
Biodynamic :The «biodynamic» designation is used for all estates certified as using biodynamic methods, as verified by one of the two official bodies, Demeter or Biodyvin. All wines produced by biodynamic methods are also certified as organic. This designation applies to recent vintages.
Organic :The «organic» designation covers all estates certified as using organic methods, as verified by one of the bodies approved by the Ministry of Agriculture, such as Ecocert. This designation applies to recent vintages.
Sustainable :The «sustainable» designation covers all estates certified as using integrated or High Environmental Value (level 3 Environmental Certification) techniques. This designation applies to recent vintages.
Evironmentally friendly :The «environmentally friendly» designation refers to estates practising environmentally friendly wine-growing techniques, but that have not opted for certification or who are still in the process of converting to organic agriculture or biodynamics. These estates may have adopted biodynamic principles (non-certified) or simply no longer use chemical products. This designation applies to recent vintages.
Natural :Wines which are produced without any added sulfur (or almost any) and with no other inputs. However, given that there is no official body to issue the natural wine label, it is based on winemakers' statements.This designation applies to recent vintages.


text:
Email: email@example.com.
Map Categories
Popular Tags
- The original images presented on this website are not the property of this website and are believed to be in the public domain. No endorsement of or affiliation with any third party is intended or implied by the presence of any information or images on this website.
You assume all risk related to your use of the images on this website, including sole responsibility for using such images in accordance with applicable law. If you believe that your copyrighted work or the copyrighted work of another party is being infringed, please contact me.


text:
We are the source for Cannon Ball Hot Sauces, Chesapeake Fire, Miles River Dry Goods & Provisions LLC.
Chesapeake Fire After years of carrying this seriously blazing habanero sauce, Bobby was able to purchase the company. Once he had the recipe, we began tracking down the finest ingredients available. After two and a half months we arrived at Mama Vida's kitchen in Randallstown Maryland, and began our first run of Chesapeake Fire. Make no mistake, this is a HOT sauce. We give it a 7, on a scale of 1-10 (if "Z" is an 11). Chesapeake Fire lends itself well to seafood, especially oyster shooters. Of course we had to do a quick quality check on the Wild Goose Amber. (great beer)
Cannon Ball Hot Sauce From the town that fooled the British, comes Cannon Ball Hot Sauces. Six great flavors that will add taste and warmth to any meal.
Miles River Dry Goods & Provisioning We finally got tired of the high salt content in the traditional Chesapeake Bay style seasoning. So Bobby set out to develop his own blend. When we started giving out samples of this, we thought we might have to tweak it a little. However, the response has been fantastic. Miles River Dry Goods & Provisions LLC proudly introduces Seafood & More with less salt and more black pepper. Try this instead of the high salt Bay seasoning you're used to. This will quickly become your favorite dry spice. Sprinkle it on burgers, rub it on a roast, use it in your favorite recipes, or shake it on seafood.
Huge Selection In Store!
- Over 1000 Hot Sauces
- More than 75 Salsa's
- 250 BBQ'S & Marinades
- Over 100 Types of Olives
- Award-Winning Chili Mixes
- Specialty Dry Rubs
- Exotic Seasonings .... and so much more!


text:
How To Make Basic Tomato Sauce with Fresh Tomatoes
If you've been eyeing those gorgeous tomatoes at the farmers market and wondering what it might take to transform them into jars of delicious red sauce, wonder no more. Here is everything you need to know to make a moderate-sized batch of tomato sauce for your pantry (or freezer!), from picking the right tomatoes to packing the sauce into jars.
Fifteen pounds of fresh tomatoes. One afternoon. Eight pints of sauce. It's go time.
Making tomato sauce isn't very hard, but it's definitely labor-intensive. Even the relatively small amount that we're making here — just enough for a few special mid-winter meals — will take you a solid afternoon of work from start to finish. If you want to make a larger batch, give yourself even more time for the project and think about recruiting some extra hands to help you out.
Choosing Tomatoes for Sauce
Any tomato that tastes good to you can be used to make tomato sauce; it's really that simple. Romas and other paste tomatoes are often recommended for canning because they generally have more flesh with less juice and fewer seeds. However, they are smaller (which means more up-front prep work), and I often find that their flavor isn't as good as other tomatoes. I used Big Boy tomatoes — your basic summer slicing tomato — for the batch I made for this post and couldn't be happier. If you like what you start with, you'll like what you finish with.
Another factor to consider is the cost of the tomatoes. Anything more than a dollar a pound, and the cost-effectiveness of this home canning project starts to plummet. A friend of mine who tries to can around 180 pounds of tomatoes each summer says she doesn't pay much attention to the particular tomato variety; she just picks up what she can find for cheap. This often means buying in bulk directly from farms or picking your own — or even better, growing your own if you can!
Making the Sauce
This sauce is the most basic tomato sauce there is — just tomatoes and some lemon juice to bump up the acidity to safe levels for canning. You can add seasonings like garlic, onions, or herbs, but I like the fact that this is a neutral base for whatever recipe I want to make, from weeknight pizzas to a fancy lasagna. Just avoid using oil if you're planning to can your sauce, as this can potentially be a source for botulism.
Chunky or Pureed Sauce?
To save ourselves a bit of work, I recommend chopping the tomatoes in a food processor or blender before cooking them. A few pulses will make a chunky sauce, and longer processing will make a very smooth sauce. Conversely, if you like a verychunky sauce, skip this step altogether and let the tomatoes break down naturally as they simmer. You can also chop the tomatoes by hand, run them through a food mill, or purée them with a stick blender after they've been cooking.
How Long to Cook the Sauce?
I give a cooking range of 30 minutes to 90 minutes (1 1/2 hours). Shorter cooking times will yield a thinner sauce with a fresher tomato flavor; longer cooking times will thicken your sauce and give it a cooked flavor. Watch your sauce as it simmers and stop cooking when it reaches a consistency and flavor you like.
Last Thoughts
If you've never made tomato sauce from fresh tomatoes before, this is a good place to start. The amount isn't overwhelming, but you'll make enough to justify the afternoon. It's also a small enough amount that you can freeze the whole batch if you don't feel like canning it.
Bottom line: Grab yourself some tomatoes and make yourself some tomato sauce this weekend. You won't regret it. Here's the recipe!
How To Make Basic Tomato Sauce with Fresh Tomatoes
What You Need
15 pounds ripe tomatoes
1/4 to 1/2 cup lemon juice or red wine vinegar
2 teaspoons salt (optional)
6 1/2-quart or larger Dutch oven or stockpot
Mixing bowls
Slotted spoon
Knife and cutting board
Food processor or blender
Jars for canning or containers for freezing
- Boil a pot of water and prep the ice bath: Bring a large Dutch oven or stockpot of water to a boil over high heat. Fill a mixing bowl with ice and water and set this next to the stove.
- Prepare the tomatoes for blanching: Core out the stems from the tomatoes and slice a shallow "X" in the bottom of each fruit.
- Blanch the tomatoes to peel them: Working in batches, drop several tomatoes into the boiling water. Cook until you see the skin starting to wrinkle and split, 45 to 60 seconds, then lift the tomatoes out with the slotted spoon and plunge them into the ice water. Continue with the rest of the tomatoes, transferring the cooled tomatoes from the ice water to another mixing bowl as they cool.
- Strip the peels from the tomatoes: When finished blanching, use your hands or a paring knife to strip the skins from the tomatoes. Discard the water used to boil the tomatoes.
- Roughly chop the tomatoes: Working in batches, pulse the tomatoes in the food processor. Pulse a few times for chunkier sauce, or process until smooth for a pureed sauce. Transfer each batch into the Dutch oven or stockpot. Alternatively, chop the tomatoes by hand. Process through a food mill for a smoother sauce. For a very chunky sauce, skip this step entirely and let the tomatoes break down into large pieces as they cook.
- Simmer the tomatoes: Bring the tomato sauce to a simmer over medium heat. Continue simmering for 30 to 90 minutes, stirring occasionally, until the sauce reaches the taste and consistency you like.
- Stir in the lemon juice and salt: When finished cooking, stir in the lemon juice or vinegar and salt. A quarter-cup is necessary to ensure a safe level of acidity for canning. Add more lemon juice or vinegar to taste.
- Preserving option 1 — freeze your sauce: Let the sauce cool, then transfer it into freezer containers or freezer bags. Sauce can be kept frozen for at least 3 months before starting to develop freezer burn or off-flavors.
- Preserving option 2 — can your sauce: Transfer the hot sauce into sterilized canning jars. Top with new, sterilized lids, and screw on the rings until finger tight. Process in a pot of boiling water for 30 minutes. Let cool completely on the counter — if any lids do not seal completely (the lids will invert and form a vacuum seal), refrigerate that sauce and use it within a week or freeze it for up to 3 months. Canned tomato sauce can be stored in the pantry for at least a year.


text:
Phase 3 Questions & Answers
This page records specific questions of Phase 3 users and the corresponding answers given by the ESO/ASG support team assuming that the provided information appears to be helpful to a broader audience.
List of FAQs
- Q&A of General Interest
- PROV keywords
- More on PROV keywords
- Encoding PROV in catalogue data 05.2016 updated
- Displaying big files
- Visualising 1D spectra
- CONTINUE FITS convention not supported 03.2014
- Additional OBSTECH values 03.2014
- Clarification of the WCS and CDELT requirements 04.2014
- NCOMBINE is now mandatory for images and 1d spectra 04.2014
- TEXPTIME is now mandatory for images, 1d spectra, and single band source lists 04.2014
- Definition of mandatory keyword 03.2014
- Programmatic access to archive and original filenames 03.2014
- Clarification of the ancillary data content 03.2014
- EXPTIME cannot be negative 04.2014
- Positioning of ORIGFILE 04.2014
- Including data from other facilities (not ESO) 05.2015
- Calibration data taken under SCIENCE category 07.2017
- Providing a DOI as bibliographic reference 06.2017
- Renaming downloaded Phase 3 products to their original file names 04.2018
- Is PROCSOFT mandatory? 01.2016
- MJD-OBS, MJD-END: now mandatory for additional data types 01.2016
- Scope of PRODCATG extended 01.2016
- Q&A: Catalogues
- Unique source identifier
- Multi-band aperture-matched source lists and band-merged catalogue-like products
- Band-merged catalogues for the deep survey fields
- Light curves
- Migrating catalogues from ASCII to FITS format
- TCOMMi and TUCDi keywords 09.2014
- Processing provenance per catalogue record (spectroscopic programs) 02.2015
- Mandatory keywords for photometric catalogues using multi-file format 08.2016
- How to deliver catalogue data using the tile-by-tile scheme 01.2016
- Definition of catalogue data links 01.2016
- Unique source identifier
- Q&A: Imaging
- Specification of a mask image
- VST tile keywords
- Imaging with inaccurate calibration
- Uncalibrated images
- NDITHER has become not mandatory for the OmegaCAM products 03.2014
- What is the correct EFFRON for median-combined SOFI images? 09.2014
- Missing PSF_FWHM image quality parameter 05.2015
- Definition of EPS_REG keyword for VISTA Public Surveys 04.2016
- Q&A: Spectroscopy
- Converting a spectrum to the Phase 3 required binary table format 08.11.2017
- Definition of keyword TOT_FLUX (total flux)
- Flux scale error keyword definition
- Statistical error in spectral coordinates
- Systematic error in spectral coordinates
- Positioning of the TFIELDS keyword
- Spectral Resolving Power (not resolution)
- Specification of a 2D spectrum
- Variable length arrays are not permitted in spectra 04.2014
- Flux error units: "%" is not permitted
- Computing EXPTIME and MJD-END for SOFI spectra
- BUNIT keyword in spectroscopic data 04.2014
- Extended object keyword definition 03.2014
- DISPELEM, OBSTECH values 08.2016
- Encoding quality information 03.2014
- Monotonicity of the wavelength array 03.2014
- Off source raw exposures 03.2014
- Definition of WAVELMIN and WAVELMAX 03.2014
- Clarification about CONTNORM 02.2015
- Preparing APEX 1-D spectra compliant to the Phase3 standard 03.2017
- Air wavelength vs. vacuum wavelength (1D spectrum data format) 07.2017
- Converting a spectrum to the Phase 3 required binary table format 08.11.2017
- Q&A: Data Cubes (Integral Field Spectroscopy)
- Associating Imaging Data to Data Cubes 13.06.2018
- How are exposure maps defined in the SDP standard? 17.09.2018 new
- How is the variation of the number of contributing exposures defined in the SDP standard? 17.09.2018 new
- Clarification of requirements for the OBJECT keyword 14.11.2018 new
- Typos
PROV keywords
Q: In the example header provided in the user documention the PROV refer to the archive file names, e.g. PROV1 = 'VCAM.2010-09-29T05:55:14.101.fits' while ours is PROV0001 = 'v20100928_00514.fit[1]'. I understand that it makes more sense for you the first one, but can you confirm this point for me please? I.e. we have to change PROV0001 to PROV1 and also look up the name of the ARCFILE in our provenance file.
A: Regarding the PROV* keywords, it is correct that the ESO/EDP standard differs from the convention used at CASU. Specifically, the ESO/EDP data standard mandates that
- the index i (i=1,..,N) of the indexed keyword PROVi is not zero-padded;
- the values of PROVi are pointers to files rather than pointers to FITS extensions, i.e. no trailing extension number in square brackets;
- the PROVi keywords reside in the primary HDU of FITS file.
Generally, the PROV pointers should point to files being archived at ESO. In the case of ESO public imaging surveys this can be either the original raw files using the ESO archive identifier like 'VCAM.2010-09-29T05:55:14.101.fits' or other product files being submitted to ESO for archival and publication.
VHS is expected to deliver tiles as primary survey products. If the PI/Co-I's choose not to submit the intermediate products, let's say pawprints, from which the tiles were created, then the PROVi keywords written in the tiles should point to the original raw files like 'VCAM.2010-09-29T05:55:14.101.fits'. The header example for the VISTA tile given in Sect. 3.2.1 of the ESO/EDP Standard (Issue 3) corresponds to this case.
Otherwise, if, based on an evaluation of the extra scientific merit to be expected, intermediate products (pawprints) are planned to be delivered as well, then the PROVi keywords written in the tiles should point to the pawprints and, in turn, the PROVi keys in the pawprints should point to the original raw files.
In the case of single-band source catalogues extracted per tile, called "source lists" in our terminology, the PROV1 key has to point to the originating tile unconditionally (cf. ESO/EDP Standard, Issue 3, Sect. 3.2.4, p.36).
For the definition of processing provenance in the context of Phase 3, including an extended set of examples, please refer to the ESO/EDP Standard, Issue 3, Sect. 2.4.
More on PROV keywords
Q: I note that the PROV keywords do not seem to be mandatory; if that is the case we do not need to provide them, right?
A: PROV keys were recommended for image data products (tile, pawprint etc.) submitted in 2011. The upgrade of the Phase 3 Infrastructure that took place in May 2012 entails the requirement saying that processing provenance is compulsory metadata for Phase 3 data products delivered thereafter.
Encoding PROV in catalogue data
Q: How to encode processing provenance (PROV) of catalogue data being submitted at the same time as the original images?
A: The processing provenance shall be specified within the catalogue files in terms of original filenames of the imaging data (a.k.a. ORIGFILE), as usual, for example:
PROV1 = 'vmc_er1_05h59-066d20_tile_j_deepimage_1403891.fits.fz'
PROV2 = 'vmc_er1_05h59-066d20_tile_ks_deepimage_1403943.fits.fz'
Catalog and imaging data can be submitted using separate Phase 3 batches (within the same Data Collection). To allow proper resolution of PROV references the imaging data must be submitted before the catalog data can be successfully validated.
Displaying big files
Q: How can I display the 9Gb fits files of the stacked UltraVISTA images?
A: You must have a 64 bit OS to display the images. It will work right away in ds9 if your machine has at least 9GByte of RAM. If not, you can use imcopy in IRAF or the stand-alone utility fitscopy that comes with CFITSIO. Compiling fitscopy is usually as simple as:
make fitscopy
You can then copy out a subsection e.g. as
fitscopy 'filename.fits[6317:42736,7063:37182]' filename.trim.fits
This particular subsection would be about 4 Gbyte (and requires about 4 Gbyte RAM to make); you can of course try something smaller. The format of the subsection is x1:x2,y1:y2 (just like in IRAF).
Visualising 1D spectra in the binary table format
Q: How can I visualise the 1D spectra stored in binary table format as defined in the ESO science data products standard?
A: Please follow the instructions here.
CONTINUE convention not supported
OBSTECH values
Q: May you please clarify what the OBSTECH keyword values are?
A: We support the OBSTECH keywords listed in the table below, in addition to those listed in the SDP standard document
|Origin of Keyword Value
Definition of mandatory keyword
Q: Can you please explain what a mandatory keyword means?
A: For keywords of type 'string' it means that both the keyword shall be present and its value shall not be blank (except for REFERENC if a refereed publication is not available at the time of the data release going public). For keywords of type 'float' or 'integer', it means that the FITS card shall not be incomplete and that a valid value shall be provided.
Programmatic access to archive and original filenames
Q: Is there a way to query the archive for the original filenames of the data?
A: Yes, please find more information about programmatic access at:
A typical query is listed below:
Clarify ancillary data content
Q: Which kind of data can be provided in an associated ancillary file?
A: An ancillary data product provided together with a data release should contain additional data that is not included in the science data product itself. The ancillary file should not replicate information present elsewhere. In particular keep in mind that Phase 3 generally mandates that the data documentation is to be provided in the release-description.pdf file. Referential information and other metadata must be defined in the header of the science file in terms of FITS keywords. ESO/ASG has the overall responsibility to assess if provided ancillary data qualify for ingestion into the ESO science archive facility.
Including data from other facilities (not ESO)
Q: We like to include in our catalogue some data originating from a non-ESO facility. Is there a flag to indicate such products?
A: Please use the dedicated boolean keyword NOESODAT in the primary header to indicate that the product includes non-ESO data:
NOESODAT = T / includes non-ESO data
Note: if the catalogue is predominantly based on ESO data then the Phase 3 keywords TELESCOP, INSTRUME and PROV should record the provenance of the ESO data component only.
Calibration data taken with DPR CATG='SCIENCE'
Q: May you please clarify whether calibration data taken with a DPR CATG ='SCIENCE' should be taken into account in the set up of the MJD-OBS, MJD-END, T/EXPTIME, NCOMBINE, TELAPSE, and PROVi keywords?
A: It can happen that some calibration data have been acquired with a DPR.CATG = 'SCIENCE'. Those calibration exposures should be excluded from the calculation of the MJD-OBS, MJD-END, T/EXPTIME, NCOMBINE, and TELAPSE keyword values. The list of PROVi keywords recording the science files originating the data product should not contain any reference to those calibration files.
Example where this situation happens:
- XSHOOTER: the OFFSET frames with DPR.TECH = 'SKY' (even though taken as DPR.CATG = 'SCIENCE') should NOT be taken into account, while the ones with DPR.TECH = 'OBJECT' are the real science data.
About providing a DOI as bibliographic reference value
Q: Can I provide a DOI as value for the REFERENC header keyword?
A: Both the 19-digit bibliographic identifier used in the Astrophysics Data System bibliographic database or the Digital Object Identifier are valid bibliographic reference information to point to the primary publication associated to a data product.
If you provide the DOI, the link should be given as in the following example:
REFERENC= 'doi:10.1051/0004-6361/201730605' / Bibliographic reference
while in the case you provide the BibCode, the link should be given as follows:
REFERENC= ' 1924MNRAS..84..308E' / Bibliographic reference
Renaming downloaded Phase 3 products to their original file names
Q: How can I rename the P3 products from their ADP names to the original file names?
A: In the case of files downloaded via the Request Handler, the correspondence between file-id and original file-name is mapped in the README file associated to each data request. The renaming commands can be extracted directly from the README file using the following shall command:
awk '/\- ADP/{ print "mv "$2, $3}' README_123456.txt
In some cases it can happen that during the downloading the ':' of the file name is replaced by a '_',
if so, please use this other command line:
awk '/\- ADP/{ print "mv "$2, $3}' README_123456.txt | awk '{gsub(/\:/, "_", $2)}1'
PROCSOFT Keyword
Q: Is the keyword PROCSOFT mandatory?
A: PROCSOFT keyword are now mandatory for all science data product files (before it was recommended but not strictly required). PROCSOFT (string data type) indicates the reduction software system including its version number being used to produce this data product.
Scope of PRODCATG extended
Q: When is PRODCATG mandatory?
A: PRODCATG becomes mandatory for associated FITS files (while before it was only mandatory for SCIENCE files). Previously the category of associated FITS files was defined by the ASSOCi keyword within the referencing science file. Now, the category must be defined by PRODCATG within the associated file using the same value that was previously assigned to ASSOCi.
ASSOCi becomes obsolete and should not be defined anymore for associated FITS files but only in case of associated files in other formats like PNG.
Unique source identifier
Errata for §188.8.131.52: the IAU naming convention provided in the SDP standard is amended to:
Every source catalogue must have a unique source identifier, defined according to the IAU recommendations for nomenclature using the schema16
<prefix> J<hhmmss.ss+-ddmmss.s>
or, alternatively,
<prefix> J<hhmmss.sss+-ddmmss.ss>
where prefix denotes the survey programme.
In case you cannot use the IAU naming convention because of duplication/deblending problems, then please be aware of what follows.
Sources in the band merged catalogues with duplication/deblending problems should still have a unique identifier.
Q: Please can you clarify if the column is to be called anything in particular and confirm it'll be OK for it to be a LONG INTEGER.
A: There is no Phase 3 requirement for a particular column name. The names must comply with the restrictions specified in ESO SDP Standard, Issue 5, Sect. 5.1.3, keyword TTYPE*. The unified content descriptor (UCD) meta.id;meta.main shall be set to identify the catalogue column that represents the source identifier. Long integer type is ok.
Here is an example:
TCOMM1 = 'Unique source identifier'
TUCD1 = 'meta.id;meta.main'
Note: TNULL1 should not be defined here as the identifier is not nullable by definition.
About multi-band aperture-matched source lists and band merged catalogues.
Q: What are the differences between multi-band aperture-matched source lists and band-merged catalogue-like products.
A: Here are some useful information on multi-band aperture-matched source lists and band-merged catalogues.
Multi-band aperture-matched source lists (FITS tables) are produced from the single band source lists and are associated with the tiles observed in different bands for one pointing sky position. The astrometric and photometric calibrations for the ra/dec and magnitudes of the sources in these lists are based on night-calibrations. E.g. these are not global calibrations. The multi-band aperture matched source lists cannot be queried for content from the ESO archive; they can be downloaded as fits tables and will refer to the ra/dec sky position of tiles they were produced from.
Multi-band (or band merged) catalogue are released at the milestones for the survey releases. The first Phase 3 submission period for catalogue data resulting from VISTA public surveys occurs between 25 May and 30 June 2012. The calibration of the astrometry and photometry is global, on the whole region covered by the release. The catalogues will be querable for content, differently from the multi-band aperture-matched source lists , i.e. the individual sources in the catalogues will be accessed via the ESO query interface.
Sources in the catalogues may be detected based on the χ2 image or other criteria, driven by the scientific goal of the project. They will not come necessarily from matching single band source lists from the CASU data reduction pipeline.
Furthermore catalogues delivered at the survey releases may contain additional data, that do not come from the VISTA observations: for example photo-z or matched information with X-ray or other multi wavelength observations, weak lensing information etc.
Band-merged catalogues for the deep survey fields
Q: What are multi-band aperture-matched source lists and band merged catalogues for the deep survey fields?
A: It deals with the specific properties of deep surveys with respect to the wide area surveys. As illustrated before multi-band aperture matched source lists are different data products from band-merged catalogues.
Multi-band aperture matched source lists may refer to shallower data products than the deep stacked tiles that are obtained from the data collected over the whole period.
In case of the deep fields, the survey teams may decide to release 1 hr or xx hrs deep tiles with associated multi-band aperture-matched source lists, which will be very valuable data-products for multi-epoch observations, for example monitoring AGN variability or SN searches. In this case the information contained in the multi-band aperture matched source lists is not equivalent to the catalogue extracted from the deep stacks, as the variability information is lost in this final catalogue.
About the multi-band aperture-matched source lists: for deep surveys, the distinction between these source lists and the catalogues expected for the survey releases is more difficult to draw. While for wide surveys the scientific quality difference is clear, it is less so for deep surveys.
Example specific for a deep field
A deep field is observed in Z, J, and Ks in a period with 28 tile-OBs in Z, 21 tile-OBs in J and 21 tile-OBs in Ks successfully executed. The related data products would be 28 tiles in Z, 21 tiles in J and 21 tiles in Ks + weight maps + single band source lists as data products for these observations.
One would then have 21 multi-band aperture matched source lists in Z, J, and Ks computed from the single-band source lists closest in time.
Light curves
Q: Are the data standards specified for light curves data products? When is the submission date for these products?
A: The ESO External Data Products Standard, Issue 3, Date 22.05.2012, now also covers multi-epoch photometric catalogues (Sect. 4.2.2) to support the Phase 3 delivery of light curves during the May/June 2012 submission period depending on survey progress.
Migrating catalogues from ASCII to FITS format
Q: How to convert an ascii file (table) to a fits file?
A: You can perform the following steps:
- Create a comma separated ascii table. For example if the table (cat1.txt) has n columns separated by white spaces:
awk '{print $1,","$2,","$3,","$...,","$n-1,","$n}' cat1.txt > cat2.txt
- Convert the new table (cat2.txt) into a fits file using the stilts tool:
stilts tcopy cat2.txt cat.fits ifmt=csv ofmt=fits-basic
stilts <stilts-flags> tcopy ifmt=<in-format> ofmt=<out-format> [in=]<table> [out=]<out-table>
- Add the missing header keywords according to the ESO External Data Products Standard.
The STIL Tool Set can be downloaded from:
For more information please check the following documentation:
TCOMMi and TUCDi keywords in catalogue data files
Q: Are TCOMMi and TUCDi keywords required in the FITS header of catalogue data files?
A: Yes, to successfully pass Phase 3 validation each catalogue data file must include the indexed keywords TCOMMi and TUCDi, one for each catalogue column. Note that Table 15 of the ESO Science Data Products Standard, Issue 5, is lacking these keywords although they are required - an inconsistency which will be corrected in a forthcoming version of the document.
Processing provenance per catalogue record (spectroscopic programs)
Q: Spectroscopic programmes like Gaia-ESO, PESSTO or zCOSMOS produce high-level results in the form of catalogues where each record contains the results of the analysis of one reduced spectrum (which is a Phase 3 product itself). How to encode the links between catalogue record and original spectra?
A: The catalogue must contain a column with a ORIGFILE or ARCFILE reference that identifies for each row the 1D spectrum from which the catalogued parameters are measured.
ORIGFILE refers to the filenames of the 1D spectra within the current release, ARCFILE refers to the ESO archive identifier of the form ADP.<timestamp>
Header listing for HDU #1:
Header listing for HDU #2:
TCOMM8 = 'FITS file name of the original spectrum'
TUCD8 = 'meta.ref'
TXLNK8 = 'ORIGFILE' / Data link to the original spectrum
Clarification regarding mandatory keywords for photometric catalogues using multi-file format
Q: Are the keywords listed in 126.96.36.199 of the ESO Data Products Standard mandatory only for the metadata file for catalogues in multi-file catalogue format?
A: No, now FILTER, FILTERi and REFERENC keywords are also required in the headers of the catalogue data files. In this way users can query catalogues tiles also selecting a specific filter. They will be returned as query results showing the bibliographic code of the related publication, enhancing its visibility.
Moreover, if possible, we encourage to define also values for the header keywords MAGLIMi, 5-sigma limiting AB magnitude for point sources, for such products, using the same indexing as for FILTERi
FILTER1 = 'Z' / Filter name
MAGLIM1 = 20.53562164306641 / 5-sigma point source limiting AB mag
FILTER2 = 'Y' / Filter name
MAGLIM2 = 20.16515922546387 / 5-sigma point source limiting AB mag
FILTER3 = 'J' / Filter name
MAGLIM3 = 19.83752250671387 / 5-sigma point source limiting AB mag
FILTER4 = 'H' / Filter name
MAGLIM4 = 19.53595924377441 / 5-sigma point source limiting AB mag
FILTER5 = 'Ks' / Filter name
MAGLIM5 = 19.46832275390625 / 5-sigma point source limiting AB mag
Catalogue data using the tile-by-tile scheme
Q: How to deliver catalogue data using the tile-by-tile scheme?
A: For catalogue deliveries using the tile-by-tile scheme, the data files (PRODCATG=SCIENCE.CATALOGTILE) must be logically associated to the catalogue meta file (PRODCATG=SCIENCE.MCATALOG) using the following scheme: MCATALOG includes the list of associated CATALOGTILEs encoded as a dedicated FITS binary table extension. The table stores the filename (ORIGFILE) of each CATALOGTILE, using one record per CATALOGTILE.
Specifically required FITS header keywords (binary table extension):
NAXIS1 = %d
NAXIS2 = %d
TFIELDS = %d
TTYPEi = 'ORIGFILE'
TFORMi = 'nA '
NAXIS2 equals the total number of CATALOGTILEs. The table must consist of one single ORIGFILE column at minimum. The table may contain more columns, having TTYPEj different from ORIGFILE, if the data provider intents to record further file parameters of interest.
Definition of catalogue data links
Q: How to define catalogue links?
A: The keywords TXP3Ri and TXP3Ci, which were previously used to define the target catalogue of a data link between two catalogues, are being replaced by the new TXRGFi keyword. TXRGFi (type character string) should declare the filename of the target catalog in terms of the ORIGFILE name.
Previous data link definition:
TXLNK3 = 'CATALOG ' / Data link type
TXP3C3 = 'VMC_CAT ' / Target catalogue
TXP3R3 = 3 / Release number
TXCTY3 = 'SOURCEID' / Target catalogue's TTYPE
New data link definition:
TXLNK3 = 'CATALOG ' / Data link type
TXRGF3 = 'vmc_er3_yjks_catMetaData.fits' / Target catalogue
TXCTY3 = 'SOURCEID' / Target catalogue's TTYPE
Note that catalogue data links point to the filename of the meta catalogue file (PRODCATG=SCIENCE.MCATALOG) in case of multi-tile catalogs.
Specification of a mask image
Q: May you please explain how to specify a mask image as an ancillary product?
A: The mask image describes the data quality of an image array by flagging bad pixels using integer numbers >0. For example: bright stars (=1), readout spikes (=2) etc. Mask value =0 indicates 'good' data. The detailed definition of mask values >1 shall be documented in the Phase 3 release description.
The mask image is a FITS file with the same dimension and number of extensions (if any) as the FITS file that contains the image data. The mask has integer data type, e.g. BITPIX = 8 or 16.
The keyword PRODCATG is to be set in the mask image:
Keywords refering to the tiling of the sky for OmegaCAM data
Q: How to fill in the values of the TL_RA, TL_DEC, and TL_OFFAN for VST data?
A: In what follows, the assumption is that the information provided by the VST survey teams in the OB does indeed refer to the nominal survey tile position.
- The position of the tile in terms of TL_RA and TL_DEC is shown in the HIERARCH ESO TEL TARG ALPHA and HIERARCH ESO TEL TARG DELTA keywords. That is, for an OB pointing to a certain coordinate for the acquisition template, the HIERARCH ESO TEL TARG ALPHA/DELTA keywords do not change for each exposure even if these are acquired at relative offsets with respect to the above reference coordinates. The exact coordinates for each exposure are logged in the RA / DEC keywords. The RA/DEC keywords in the image headers contain the precise position on the sky of each individual exposure.
- The unit and format of "HIERARCH ESO TEL TARG ALPHA" and "HIERARCH ESO TEL TARG DELTA" are HHMMSS.TTT and DDMMSS.TTT, respectively.
- The tile orientation is recorded in HIERARCH ESO ADA POSANG. POSANG = 0 means the usual N/S orientation, with North and East being aligned with positive y and x. Within the fixed x-y coordinate system, the North axis rotates clockwise with increasing POSANG towards East, thus following the same sign convention as the position angle on the sky. Hence: TL_OFFAN = -POSANG.
Finally, note that by definition, the TL_* keywords are identical for all data belonging to the same tile.
About imaging data without accurate astrometric/photometric calibration
Q: How to submit image data without accurate astrometric/photometric calibration via Phase 3?
A: Imaging data need to be characterized in terms of their astrometric registration (WCS), photometric scale (PHOTZP) and dynamic range (ABMAGLIM, ABMAGSAT) in order to qualify as Science Data Product according to the ESO/SDP standard.
Taking into account that the accuracy of these calibrations varies depending on the scientific goals for which the data was obtained, the ESO/SDP standard does not specify a fixed level of accuracy for calibrations but allows to encode the quality using specific keywords, namely CRDERi, CSYERi, and PHOTZPER.
It means in practical terms that the image WCS may be defined based on the information given in the raw data if it is infeasible to register the image with respect to an astrometric reference catalogue. Similarly, the photometric scale and depth of the image data may be estimated based on the nominal instrumental characteristics (default instrumental zero points, exposure time calculator) if photometric standards have not been obtained as part of the observation. The larger uncertainty associated with the estimated photometric properties needs to be expressed by setting PHOTZPER to an appropriate value.
Specification of an uncalibrated image
Q: How to submit an image without photometric and astrometric calibration?
A: An image without photometric and astrometric calibration can be submitted as an associated file of a main SCIENCE product (e.g. an acquisition image associated to a SCIENCE.SPECTRUM).
The uncalibrated image must include the following keyword definition within the FITS header:
EFFRON for median-combined SOFI images
Q: What is the correct EFFRON for median-combined SOFI images?
Example: There are 7 raw images, each resulting from averaging together 5 detector integrations (NDIT = 5). A science product is generated by reducing and median-combining those 7 raw images.
In this case:
EFFRON = 12 * sqrt(PI/2) / sqrt( 7 * 5)
where PI is 3.14159, and 12 is the detector readout noise of SOFI in electrons.
Missing PSF_FWHM image quality parameter
Q: Using the MEFIMAGE format in case of chip-by-chip processing of OmegaCAM data it occasionally happens that the PSF_FWHM quality parameter cannot be determined for one of the chips, normally due to the lack of suitable point-like reference objects just in this field. The PSF_FWHM recorded with the other detectors demonstrates that the overall image quality appears to be ok. How to define PSF_FWHM for the problematic detector chip (MEFIMAGE format)?
A: The MEFIMAGE format requries PSF_FWHM to be defined separately for each detector, i.e. image extension. The valid range is PSF_FWHM > 0. If PSF_FWHM cannot be determined for one of the detectors then the special value -1 should be assigned to PSF_FWHM in the respective FITS extension:
Note: the PSF_FWHM special value is not supported for the SCIENCE.IMAGE format i.e. for resampled survey tile images.
Definition of EPS_REG keyword for VISTA Public Surveys
Q: How to assign a value to the EPS_REG keyword?
A: The EPS_REG keyword should uniquely refer to the name of the survey region or area. The keyword values are defined as follows:
|Public Survey
As an example, the FITS headers for the VIDEO survey are defined as follows:
EPS_REG = 'VIDEO/CDFS' / ESO public survey region name
EPS_REG = 'VIDEO/ES1' / ESO public survey region name
EPS_REG = 'VIDEO/XMM' / ESO public survey region name
Note: to identify individual survey fields, the OBJECT keyword should be used instead. Examples are:
OBJECT = 'VIDEO/ES1-North ' / Target designation OBJECT = 'VIDEO/ES1-South ' / Target designation OBJECT = 'VIDEO/CDFS2' / Target designation OBJECT = 'VIDEO/XMM3' / Target designation
Producing Phase 3 compliant spectra
Q: How can I convert my spectrum to the binary table format required by tha Phase 3 Standard?
A: You can use the following Python script (requirements: Python-2.7 or greater, astropy library) but please make sure to modify it by providing the correct values for the required FITS header keywords to be added to the file. To help the users the script already includes the commands to add all the Phase 3 mandatory keywords but when the value must be inserted by the user, the line is commented. Please provide the correct value and de-comment the line in order to generate a Phase 3 complaint file.
- In case the original spectrum is an image with the wavelength in the WCS, use this script. You can give it a try by using this input file. The script should output the following converted spectrum.
Total flux keyword definition
Flux scale error keyword definition
Q: May you please clarify the definition of the FLUXERR keyword for spectroscopic observations?
A: The FLUXERR is a mandatory quantity that provides the uncertainty on the flux scale. It applies to spectroscopic data with FLUXCAL set to 'ABSOLUTE'. In this case, the FLUXERR value is expressed as a percentage with values between 0 and 100, unless its value cannot be determined, in which case the special value -2. shall be used.
If the spectroscopic data are of type FLUXCAL = 'UNCALIBRATED', the FLUXERR keyword shall be set to -1.
Statistical error in spectral coordinates
Q: May you please clarify the relation between the LAMRMS and the SPEC_ERR keywords for spectroscopic observations?
A: The keyword LAMRMS refer to a well defined measurement on the calibration data whereas the keyword SPEC_ERR refer to an estimate of the error in the science data that might come from LAMRMS or other information.
More precisely, LAMRMS is the root-mean-square of the residuals, defined as:
LAMRMS = sqrt( sum_i(R_i2)/N )
where R_i= residual of wavelength solution for i-th arc line, N = numbers of arc lines = LAMNLIN.
It is an estimator for the uncertainty in each residual under the assumption that all uncertainties are equal and that the model that was subtracted is the correct/appropriate model for the data (so that the errors are random and not systematic).
Identifying a best estimate for SPEC_ERR requires the PI's judgement. In most cases, including UVES and XSHOOTER, the formula SPEC_ERR = LAMRMS / sqrt(LAMNLIN) is a good approximation if the scatter is mainly due to random measurements errors and those errors are similar for all lines.
Note that the value of LAMRMS / sqrt(LAMNLIN) is a lower limit to SPEC_ERR.
Systematic error in spectral coordinates
Q: May you please clarify the definition of the SPEC_SYE keyword for spectroscopic observations?
A: The keyword SPEC_SYE aims at capturing the systematic error in spectral coordinate and is expressed in nanometers. Possible sources of systematic error include any residual offset of the wavelength calibration and any error related to broadening of the lines due to the observation setup and the observation conditions.
If systematic uncertainties are known to represent an insignificant contribution to the overall error budget on the wavelength axis, or all the systematic errors have been accounted for in the submitted data product spectrum, then SPEC_SYE can be set to zero.
Position of the TFIELDS keyword in the spectroscopic extension header
Q: What is the correct position of the TFIELDS keyword in the binary table extension of a spectroscopic observation?
A: As per the FITS standard, the TFIELDS keyword that specifies the number of fields in each row of the binary table must be the 8th keyword in the FITS extension containing the binary table.
Please note that the current version of the Science Data Product standard (v5) will require an update to comply to the FITS standard.
Spectral resolving power or resolution?
Q: Should I provide the resolution or the resolving power for a 1D spectrum?
A: The SPEC_RES FITS keyword must represent the spectral resolving power (defined as Lambda / Delta_Lambda), and not the spectral resolution. SPEC_RES is therefore a dimensionless (floating point) number.
Please note that the definition of the SPEC_RES keyword in paragraph 2.12 of the Science Data Product standard, Issue 5, is to be amended.
Specification of a 2D spectrum
Q: How to submit wavelength calibrated and distortion corrected 2D spectra?
A: A 2D spectrum denotes the 2D array with one axis oriented along the dispersion direction (calibrated in wavelength), the other axis being the spatial dimension, normally oriented along the slit. Wavelength calibrated and distortion corrected 2D spectra can be submitted as associated files of the SCIENCE.SPECTRUM products. They must include the following keyword definition within the FITS header:
Variable length arrays
Q: Are variable length arrays supported in the FITS binary table of a 1D spectrum?
No, variable length arrays are not supported in the spectral case.
The 1D spectrum is serialised in a binary table as a single record, with as many cells as needed (e.g. one for the wavelength, one for the flux, etc.), each cell containing one array of data points, and with arrays across all cells of equal size. Despite being supported by FITS, the usage of variable length arrays is not allowed in Phase3, as such format is not well supported by the existing spectral tools.
Please make sure that:
Computing EXPTIME and MJD-END of SOFI spectra
Q: How to compute the EXPTIME and MJD-END of a SOFI spectrum?
The EXPTIME value of a Phase 3 product must be set to the total integration time on target. In the case of a single SOFI observation, the correct value can be computed using the following formula:
where DIT and NDIT are to be found in the raw header, e.g.:
HIERARCH ESO DET DIT = 90.0000000 / Integration Time
HIERARCH ESO DET NDIT = 3 / # of Sub-Integrations
If instead the Phase 3 product is the result of a co-addition of multiple exposures, then obviously the EXPTIME will be the sum of the individual DIT * NDIT values.
NOTA BENE: The counts in a raw data file always correspond to DIT seconds. However, a single raw data file represents a total integration time of NDITxDIT, because the counts in the file are the average of NDIT sub-integrations, each of DIT seconds!
The end time of a Phase 3 SOFI 1d spectrum product (MJD-END) must be computed using the following formula:
MJD-END = MJD-OBS of the last raw observation + NDIT * ( DIT + 1.8) / 86400
where the 1.8 seconds accounts for the necessary overheads, and 86400 scales back from seconds to days.
EXT_OBJ keyword definition
Q: Q: May you please clarify the definition of the EXT_OBJ keyword for spectroscopic observations?
The EXT_OBJ keyword is mandatory for External Data Products, e.g. Spectroscopic Public Surveys.
The keyword EXT_OBJ is not applicable to XSHOOTER Internal Data Products, i.e. the keyword must not be listed in the header. It means the property is unknown.
For GIRAFFE:
EXT_OBJ = F / True if extended object
For pointlike UVES/Echelle data:
EXT_OBJ = F / True if extended object
DISPELEM values
Q: May you please explicitly list the possible keywords values that a spectrum taken with a specific instrument can take?
A: The table below shows some examples of the possible values for the keywords TELESCOP, OBSTECH and DISPELEM. If you still have doubts or the instrument you are looking for is not listed, do not hesitate to contact us.
|Keyword not aplicable
|HARPS Echelle
* When combined
Encoding quality information
Q: May you please explain how to encode quality information in 1D spectra?
A: Relaxing the restrictions given in SDP standard v5, page 53, the data quality of each pixel is encoded in terms of the sum of powers of 2. Each 'bit' corresponds to a quality condition. Quality default to 0, i.e. good data.
Off source raw exposures
Q: May you please clarify whether off source raw exposures should be taken into account in the set up of the EXPTIME, NCOMBINE, MJD-OBS, MJD-END and PROVi keywords for 1D spectra?
A: Off source raw exposures should be excluded from the calculation of the EXPTIME, NCOMBINE, MJD-OBS, and MJD-END keywords values. The list of PROVi keywords should not contain any reference to off source raw exposures.
Definition of WAVELMIN and WAVELMAX
Q: May you please clarify the definition of the WAVELMIN and WAVELMAX keywords on page 20, section 2.11 of the SDP standard, v.5?
A: For 1-D extracted spectra (SCIENCE.SPECTRUM):
WAVELMIN and WAVELMAX should describe the minimum and the maximum wavelengths in nanometers outside of which the described spectrum does not carry any valuable scientific information. For example, if a spectrum is zero-padded on the lower wavelengths, then the WAVELMIN should not be lower than the wavelength associated to the first bin where the spectrum has a flux > 0.
Of course, WAVELMIN cannot be lower than SPECTRUM.WAVE[1], nor higher than SPECTRUM.WAVE[NELEM].
Similarly, the WAVELMAX should provide the wavelength value of the last useful wavelength bin after which the spectrum is known not to carry any scientific value.
It must be true that:
where NELEM is the pixel length of the wavelength array.
For 3-D data cubes (type "CUBE.IFS") WAVELMIN and WAVELMAX correspond to the physical wavelenth (nm) of the first and last plane of the science data cube carrying scientifically useful information.
Clarification regarding CONTNORM
Q: Which value should take the keyword CONTNORM in the case I provide two flux arrays, one normalized and the other not?
A: If multiple flux arrays are provided, then
and the Spectral Data Model v2.0 applies (VOCLASS = 'SPECTRUM V2.0').
For example, if field 2 represents the continuum-normalised spectrum (field 3 its error)
and field 4 the non-normalised spectrum (field 5 its error), the TUTYPn are:
TUTYP1 = 'spec:Data.SpectralAxis.Value' / 'IVOA data model element for field 1'
TUTYP2 = 'spec:Data.FluxAxis.Value' / 'IVOA data model element for field 2'
TUTYP3 = 'spec:Data.FluxAxis.Accuracy.StatError' / 'IVOA data model element for
TUTYP4 = 'eso:Data.FluxAxis.Value' / 'ESO element for field 6'
TUTYP5 = 'eso:Data.FluxAxis.Accuracy.StatError' / 'ESO element for field 7'
Moreover the UCD must indicate which one is the continuum-normalised spectrum using the arith.ratio token
and indicate which one is the main one, by placing the meta.main token
at the end of the TUCD2 and TUCD3:
TUCD2 = 'phot.flux.density;em.wl;arith.ratio;meta.main'
TUTYP2 = 'spec:Data.FluxAxis.Value'
TUCD3 = 'stat.error;phot.flux.density;meta.main'
TUTYP3 = 'spec:Data.FluxAxis.Accuracy.StatError'
TUCD4 = 'phot.flux.density;em.wl'
TUTYP4 = 'eso:Data.FluxAxis.Value'
TUCD5 = 'stat.error;phot.flux.density'
TUTYP5 = 'eso:Data.FluxAxis.Accuracy.StatError'
Preparing APEX 1-D spectra compliant to the Phase3 standard
Q: Could you please provide some information regarding the format of APEX 1-D spectra?
A: The format defined in the Phase 3 SDPS for 1-D spectral products applies also in the case of APEX reduced spectra, with few modifications:
1. The following keywords defined as mandatory for spectral products do not apply in the case of APEX spectra:
2. While the keyword FEBE1 indicating the Frontend-backend combination becomes mandatory in this case.
Example of the values of some specific keywords:
Primary header
ORIGIN = 'APEX' / Facility
TELSCOP = 'APEX-12m' / Telescope name
INSTRUME= 'APEXHET' / Instrument name
FEBE1 = 'HET230-XFFTS2' / Frontend-backend combination
OBSTECH = 'SPECTRUM' / Technique of observation
PRODCATG= 'SCIENCE.SPECTRUM' / Data product category
Extension header
EXTNAME = 'SPECTRUM' / FITS Extension name
TTYPE1 = 'FREQ ' / Label for field 1
TUTYP1 = 'Spectrum.Data.SpectralAxis.Value'
TUNIT1 = 'GHz ' / Physical unit of field 1
TUCD1 = 'em.freq ' / UCD of field 1
TDMIN1 = 229.011 / Start in spectral coord.
TDMAX1 = 233.000 / Stop in spectral coord.
TTYPE2 = 'FLUX ' / Label for field 2
TUTYP2 = 'Spectrum.Data.FluxAxis.Value'
TUNIT2 = 'mJy ' / Physical unit of field 2
TUCD2 = 'phot.flux.density;em.freq' / UCD of field 2
TTYPE3 = 'ERR ' / Label for field 3
TUTYP3 = 'Spectrum.Data.FluxAxis.Accuracy.StatError'
TUNIT3 = 'mJy ' / Physical unit of field 3
TUCD3 = 'stat.error;phot.flux.density;em.freq' / UCD of field 3
Please also note that the values of the following keywords need to be provided in nm:
WAVELMIN= 1291867.18750 / [nm] Minimum wavelength
It corresponds to the value of TDMAX1 converted from GHz to nm (conversion factor: 299792458)
WAVELMAX= 1309075.80566 / [nm] Maximum wavelength
It corresponds to the value of TDMIN1 converted from GHz to nm (conversion factor: 299792458)
SPEC_BIN= 111.744273793 / [nm] Wavelength bin size
SPEC_VAL= 1300471.49658 / [nm] Mean Wavelength
SPEC_BW = 17208.6181641 / [nm] Bandpass Width Wmax – Wmin
The following link may be useful to reconstruct the provenance information, it provides the mapping between the original file name to the archive id, and calculating the exposure time:
Air wavelength vs. vacuum wavelength (1D spectrum data format)
With respect to an earlier version this specification has been revised on 18/07/17 to the effect that TTYPE1 = 'WAVE' is independent of air or vacuum wavelength.
Q: How is calibration with respect to air wavelength indicated in the one-dimensional spectrum data format?
A: To discriminate wavelength measured in dry air (at standard temperature and pressure) from the wavelength measured in vacuum, the ESO/SDP one-dimensional spectrum data format requires TUCD1 to be set to 'em.wl;obs.atmos' and 'em.wl', respectively (see below).
For improved human readability when browsing the FITS header, it is recommended to add a respective comment to the line defining the TUCD1 keyword.
When the spectral axis is given in air wavelength:
TUCD1 = 'em.wl;obs.atmos' / Air wavelength
When the spectral axis is given in vacuum wavelength:
TUCD1 = 'em.wl' / Vacuum wavelength
Note: WAVELMIN and WAVELMAX need to be specified in either air or vacuum wavelength consistent with the definition of the spectral axis.
Associating Imaging Data to Data Cubes
Q: Definition of PRODCATG in case of multiple associated images.
A: Each data set must be associated by one unique white light image. Further images, like line images, may be associated in addition. To allow unique identification of the white light image, the following scheme of labeling must be adopted:
- if there are multiple images associated to the data cube, the white light image (and only this one) must be labeled PRODCATG=ANCILLARY.IMAGE.WHITELIGHT. Unless otherwise specified, the other images need to be labeled by the default PRODCATG=ANCILLARY.IMAGE.
- if there is only the white light image associated it is recommended to label it PRODCATG=ANCILLARY.IMAGE.WHITELIGHT, but PRODCATG=ANCILLARY.IMAGE is also accepted.
Exposure Map Definition
Q: How are exposure maps defined in the SDP standard?
A: In the context of co-adding multiple exposures, the exposure map records the variation of the accumulated exposure time (in seconds) of 2D image mosaic and 3D IFU data cubes per pixel and per spaxel, respectively. It encodes the pattern of multiple offset exposures being combined into the final product while taking any possible masking of bad or invalid pixels into account.
The exposure map is indicated by the FITS keyword in the primary header:
Dimensions: The exposure map is a 2D FITS image associated to the main science data as an ancillary file. It shares the dimensions (AXIS1, AXIS2), WCS definitions and number of image extensions (if any) with the 2D image mosaics, or, in case of 3D IFU data cubes, the exposure map inherits the dimensions and WCS definition of the first two axis of the data cube (AXIS1, AXIS2, etc).
Units and data encoding: The exposure map encodes the total exposure time per pixel/spaxel in units of seconds (BUNIT = 's' / exposure time in seconds) using floating point decimals (BITPIX = -32) or 16 bit scaled decimals (BITPIX = 16, see FITS standard).
The total exposure time per pixel is the sum of the exposure times of the exposures contributing to the given pixel/spaxel possibly including fractional contributions depending on the interpolation scheme.
The exposure map is constraint to values >0 for data pixels/spaxels representing a valid signal, or value=0 for void pixels/spaxels. Note: It is recommended to set the values of void pixel/spaxel in the science data to NaN.
BLANK, NaN or any other special value are not allowed in the exposure map.
Relation to the EXPTIME keyword: EXPTIME, to be recorded in the header of the main science file, is defined to be the median of the pixels values of the exposure map excluding any value=0 pixel.
Data compilation: If the effective exposure time varies within the science image or data cube, it is strongly recommended to provide the exposure map along with the main science file.
Note: The exposure map does not serve as substitute for the WEIGHTMAP.
Pixel Count Map Definition
Q: How is the variation of the number of contributing exposures defined in the SDP standard?
A: In the context of co-adding multiple exposures, the pixel count map records the variation of the number of contributing exposures of 2D image mosaic and 3D IFU data cubes per pixel and per spaxel, respectively.
If the contributing exposures have different exposure times, the pixel count map does not apply, and the exposure map should be associated instead.
The pixel count map is indicated by the FITS keyword in the primary header:
Dimensions: The pixel count map is a 2D FITS image associated to the main science data as an ancillary file. It shares the dimensions (AXIS1, AXIS2), WCS definitions and number of image extensions (if any) with the 2D image mosaics, or, in case of 3D IFU data cubes, the pixel count map inherits the dimensions and WCS definition of the first two axis of the data cube (AXIS1, AXIS2, etc).
Units and data encoding: The pixel count map encodes the total number of contributing exposures per pixel/spaxel as integer number (BUNIT = ' ' / dimensionless) using 16 bits (BITPIX = 16, see FITS standard).
The pixel count map is constraint to integer values >0 for data pixels/spaxels representing a valid signal, or value=0 for void pixels/spaxels. Note: It is recommended to set the values of void pixels/spaxels in the science data to NaN.
BLANK or any other special value are not allowed in the pixel count map.
Data compilation: If the effective exposure time varies within the science image or data cube the pixel count map may be optionally provided along with the main science file in addition to the exposure map.
Clarification of requirements for the OBJECT keyword
Q: Are OBJECT keywords in the FITS extension of SCIENCE.CUBE.IFS required? Is the specific suffix indicating the type of extensions (i.e. data/stats/err) required?
A: No, the requirement for the OBJECT keyword in the extension of data of type SCIENCE.CUBE.IFS has been dropped. It is optional now.
If such keyword does exist in the extensions, and space permits, it is recommended to adopt the OBJECT keyword value from the primary header and to append an indicative suffix for the type of extension.
List of typos in the SDP standard v.5
Typo: Page 47 of the SDP standard, v.5
Fix: The PRODCATG for the OmegaCAM pawprint should be set to SCIENCE.MEFIMAGE.
Typo: Page 33 of the SDP standard, v.5
Fix: The 'ancillary.weightmap' value should be uppercased on the fourth line of the page 33.
Typo: Section 4.1 of the SDP standard, v.5
Fix: In case the spectral data have been calibrated to absolute density, the flux scale should be given in physical units, e.g. in erg/s/cm2/A. 'A' should be 'Angstrom' instead.
Typo: Section 2.4.3 of the SDP standard, v.5
Fix: It should read 'exceeding 9999 records'.
Typo: Page 17 of the SDP standard, v.5
Fix: The format string should be TFORM1 = '35A'.
Phase 3 Quick Links
Integral Field Spectroscopy: 3D Data Cubes [PDF]
Grantecan products: Spectra and Images [PDF]
Interferometric Data: PIONIER [PDF]
Get template for the data release description


text:
UNION, KY (August 8, 2009) – Jimmy Mars of Menomonie, WI continued his prowess in major dirt late model events as he passed race leader Don O'Neal of Martinsville, IN on the final lap to win the $50,000 27th Annual Sunoco Race Fuels North/South 100 Presented by Lucas Oil on Saturday Night at Florence Speedway. O'Neal, who led laps 24 through 99 saw Mars come the 15th starting spot and pass him in turn four as the two headed to the checkers; Mars took the win by a car length. Trailing Mars and O'Neal across the stripe were Scott Bloomquist of Mooresburg, TN; Earl Pearson, Jr. of Jacksonville, FL; and Jimmy Owens of Newport, TN.
Pole sitter Joe Armes took the lead at the start of the 100 lap race with Don O'Neal moving into second place followed by 2-time event winner, Steve Shaver, R.J. Conley and Scott Bloomquist. Armes and O'Neal then diced it out for the lead as the two entered traffic by lap eleven.
O'Neal raced side-by-side with Armes for the lead for two consecutive laps, but Armes maintained the lead at the scoring line. With 15 laps in the books it was a great battle for the lead with Armes and O'Neal as Shaver was closing the gap in the race for the lead.
On lap 24, O'Neal threw a slider on Armes in turn four as he cleanly passed him to take over the lead. O'Neal then started to open up some distance between himself, Armes, Shaver, Conley and Bloomquist. The top five in the running order remained the same until the first and only caution of the race came out for a slowing Will Vaught on lap 31.
On the restart O'Neal led the Delaware double file restart as Armes slipped back to fourth as Shaver and Bloomquist climbed to second and third. O'Neal built a straightaway lead ten laps into the green flag run and with 45 laps in the books. O'Neal was well out in front followed by a battle royale between Shaver and Bloomquist for second.
O'Neal re-entered traffic at the halfway mark but he still maintained a huge lead as Bloomquist passed Shaver on lap 49 after the two raced against each other for several circuits. Pearson, who had started in the outside of the front row lost several spots at the start of the race, but regrouped as he marched his way up to third passing Shaver on lap 55.
With 40 laps to go O'Neal was in command still holding a straightaway advantage over his competitors as Bloomquist and Pearson were putting on a show for second as the top two in the Lucas Oil Late Model Dirt Series fought tooth and nail for not only track position, but for points.
With 25 to go O'Neal had to contend with two cars he was trying to lap in front of him; as Bloomquist and Pearson now had company,; Mars was now in the thick of things as he climbed from his 15th starting slot to put the heat on Bloomquist and Pearson which began a three-way battle now.
O'Neal was still the car they were all trying to catch and as the laps were winding down. The trio of Bloomquist, Pearson and Mars were closing ever so slightly on O'Neal. Mars then caught up to Pearson and made a move to the inside of Pearson as he passed him for third with nine laps to go in the race.
Mars then cleared Bloomquist for second on lap 93, but it looked like at this point O'Neal had a big enough lead and that Mars would need a caution to make it close at the end, but Mars quickly made up ground in a hurry and with two laps to Mars had cut the lead to two car lengths.
O'Neal was holding on for dear life as two took the white flag as Mars closed right up on O'Neal as the two entered the last lap. Coming off of turn two heading down the backstretch Mars was able to get low on O'Neal as the two race side-by-side into turn number three. Mars was able to have enough momentum as the two came off of turn four Mars passed O'Neal in an incredible ending. Mars took the $50,000 first place money denying O'Neal his first Crown Jewel win.
In the Lucas Oil Victory Lane for the second time this year, Mars savored a win which was his second straight $50,000 win in two weeks. "Man I can't believe it, "said the 37-year old racer as he did an interview for SPEED Channel who was on hand to tape the race. "I didn't think we had a shot at him (O'Neal), but the car kept getting better and better towards the end and I caught up to him quicker than I thought I could and without any cautions, but he drove a heck of race, I mean he was out of sight there for a long time, but this is just unbelievable to win back-to-back $50,000 races with this kind of competition here, it sure feels good and I hope this roll continues," said Mars who captured the USA Nationals in Wisconsin a week earlier.
The win for Mars marked the 8th win in the last eleven $20,000 to win or more dirt late model events for either himself or Brian Birkhofer; the only two drivers who pilot the M-B Customs Chassis. Mars' winning number 28 car has a Pro Power Racing Engine and is sponsored by Deppe Enterprises, Baileigh Industrial, BSB Manufacturing, ChevytownUSA.com, T.L. Sinz Plumbing, Hoosier Tires and VP Racing Fuels.
O'Neal's disappointment in finishing second was evident on his face afterwards. "I thought we had that one in the bag, but it just shows you it's not over until the checkered flag comes out, Jimmy made a great move there on the last lap and I couldn't do anything about it," said the driver of the Racing United Marketing, /Jay Dickens Racing Engines/MasterSbilt Monte Carlo SS.
Bloomquist took third in his Miller Brothers Coal/Hawkeye Trucking/Bloomquist Race Cars Monte Carlo SS as he now holds a 185 point lead over Pearson, who finished fourth in the Bobby Labonte Racing/J4 Liquid Energy/MasterSbilt Race Car entry as Owens took fifth in the Mike Reece/Reece Monuments/Bloomquist Race Cars Ford Fusion.
Completing the top ten were Joe Armes of Petros, TN; Skip Arp of Georgetown, TN; Billy Moyer of Batesville, AR; Wendell Wallace of Batesville, AR; and R.J. Conley of Wheelersburg, OH.
To find out more about the Lucas Oil Late Model Dirt Series, log on to www.lucasdirt.com or call the series office at (951) 532-2503.
Lucas Oil Late Model Dirt Series
Race Summary
Saturday Night, August 8th, 2009
Sunoco Race Fuels North/South 100 Presented by Lucas Oil
Florence Speedway – Union, KY
PRC Fast Time: Scott Bloomquist / 17.295 seconds
Hawk Brake First Heat (12 Laps-Top 3 Advance): Joe Armes, Scott Bloomquist, Tim McCreadie, Will Vaught, Wayne Chinn, Justin Rattliff, Duane Chamberlain, Brandon Green, Jesse Lay, Adrian Nichols, Jeff Raisor, Michael Walker, Jason Keltner-DNS
Hawk Brake Second Heat (12 Laps-Top 3 Advance): Don O'Neal, Jordan Bland, Jimmy Mars, Clint Smith, Rick Combs, Brad Neat, Jeff Alsip, Tim Prince, Adam Dixon, Brian Birkhofer, Steve Duderstadt, D.J. Wells-DNS
AFCO Racing Products Third Heat (12 Laps-Top 3 Advance): RJ Conley, Josh Richards, Dustin Neat, Scott James, John Blankenship, Eddie Carrier Jr., Dustin Linville, Tyler Reddick, Jerry Bowersock, Jason Smith, Bob Lanter, Dale McDowell, Josh McGuire-DNS
Tiger Rear Ends Fourth Heat (12 Laps-Top 3 Advance): Earl Pearson Jr., Skip Arp, Darrell Lanigan, Wendell Wallace, Ray Cook, Jason Jameson, Jerry Rice, Shannon Babb, Josh Williams, John Gill, Tony Knowles, Troy Cruse, Donnie Moran-DNS
Hawk Brake Fifth Heat (12 Laps- Top 3 Advance): Steve Shaver, Steve Francis, Jimmy Owens, Steve Casebolt, David Spille, Matt Miller, Mark Douglas, Dan Schlieper, John Mason, Brett Wyatt, Steve Landrum, Gary Engle
Hawk Brake Sixth Heat (12 Laps- Top 3 Advance): Billy Moyer, Bart Hartman, Eric Wells, Chris Wilson, Eric Jacobsen, Victor Lee, Jeep VanWormer, Freddy Smith, David Breazeale, Robby Hensley, Whitney McQueary, Mike Marlar, David Webb-DNS
Mason Racin' Rebel Shock Dyno First B-Main (15 Laps-Top 2 Advance): Will Vaught, Clint Smith, Scott James, John Blankenship, Eddie Carrier Jr., Wayne Chinn, Justin Rattliff, Duane Chamberlain, Brad Neat, Brandon Green, Dustin Linville, Jerry Bowersock, Rick Combs, Jesse Lay, Tyler Reddick, Adrian Nichols, Jason Keltner, Adam Dixon, Jason Smith, Michael Walker, Jeff Raisor, Bob Lanter, Steve Duderstadt, Tim Prince, Chris Combs-DNS, Dale McDowell-DNS, Jeff Alsip-DNS, Brian Birkhofer-DNS, D.J. Wells-DNS, Josh McGuire-DNS
Wiles Drive Shafts Second B-Main (15 Laps-Top 2 Advance): Mike Jewell, Wendell Wallace, Ray Cook, Steve Casebolt, Chris Wilson, Eric Jacobsen, Jason Jameson, Victor Lee, Jerry Rice, Jeep VanWormer, David Spille, Matt Miller, Mark Douglas, Josh Williams, John Gill, Freddy Smith, Dan Schlieper, David Breazeale, Robby Hensley, Tony Knowles, John Mason, Brett Wyatt, Steve Landrum, Troy Cruse, Gary Engle, Shannon Babb-DNS, Whitney McQueary-DNS, Mike Marlar-DNS, Donnie Moran-DNS, David Webb-DNS
17th Annual Sunoco Race Fuels North/South 100 Presented by Lucas Oil
Feature Finish (100 Laps): Jimmy Mars, Don O'Neal, Scott Bloomquist, Earl Pearson Jr., Jimmy Owens, Joe Armes, Skip Arp, Billy Moyer, Wendell Wallace, R.J. Conley, Tim McCreadie, Bart Hartman, Steve Shaver, Eric Wells, Steve Francis, Josh Richards, Ray Cook, Dustin Neat, Dale McDowell, Will Vaught, Darrell Lanigan, Brad Neat, Clint Smith, Jordan Bland, Jerry Rice, Mike Jewell
Finish (Start) Car Number Driver Name
1. (15) #28M Jimmy Mars
2. (3) #71 Don O'Neal
3. (7) #0 Scott Bloomquist
4. (2) #44 Earl Pearson Jr.
5. (16) #20 Jimmy Owens
6. (1) #77 Joe Armes
7. (8) #31 Skip Arp
8. (6) #21 Billy Moyer
9. (22) #88 Wendell Wallace
10. (5) #71c R.J. Conley
11. (13) #4 Steve Shaver
12. (12) #Bart Hartman
13. (4) #30 Steve Shaver
14. (18) #18E Eric Wells
15. (10 #11F Steve Francis
16. (11) #1 Josh Richards
17. (24) #53 Ray Cook
18. (17) #25 Dustin Neat
19. (23) #Dale McDowell
20. (19) #1V Will Vaught
21. (14) #29 Darrell Lanigan
22. (26) #41N Brad Neat
23. (21) #44C Clint Smith
24. (9) #12x Jordan Bland
25. (25) #11R Jerry Rice
26. (20) #9J Mike Jewell
Race Statistics
Entrants: 78
Lap Leaders: Joe Armes (Laps 1-23); Don O'Neal (Laps 24-99); Jimmy Mars (Lap 100)
Caution Flags: Lap 31 (Will Vaught)
Lucas Oil Late Model Dirt Series Provisionals: Dale McDowell, Ray Cook
Emergency Provisional: Brad Neat
PBM/Erson Cams Hard Charger of the Race: Jimmy Mars
Allstar Performance Performer of the Race: Scott Bloomquist
K&N Filters Clean Pass of the Race: Wendell Wallace
Quarter Master Rookie of the Race: none
Comp Cams Engine Builder of the Race: Pro Power Racing Engines
Time of the Race: 37 minutes 56 seconds
2009 Championship Points Standings
1. Scott Bloomquist (Mooresburg, TN) 5195
2. Earl Pearson Jr. (Jacksonville, FL) 5010
3. Jimmy Owens (Newport, TN) 4950
4. Dale McDowell (Chickamauga, GA) 4860
5. Don O'Neal (Martinsville, IN) 4770
6. Ray Cook (Brasstown, NC) 4565
7. Steve Casebolt (Richmond, IN) 4470
8. Brad Neat (Dunnville, KY) 4235
9. Eric Jacobsen (Seacliffe Beach, CA) 3985
10. John Blankenship (Williamson, WV) 3845
11. Dan Schlieper (Sullivan, WI) 3695
12. David Breazeale (Four Corners, MS) 3485
13. Freddy Smith (Seymour, TN) 3130
16. Michael Walker (Franklin, TN) 2545
2009 Quarter Master Rookie of the Year Points Standings
1. John Blankenship (Williamson, WV) 3845
2. David Breazeale (Four Corners, MS) 3485
3. Michael Walker (Franklin, TN) 2545 4. Jeep VanWormer (Pinconning, MI) 1685