Librarians and library staff members from all types of libraries are invited to be charter members of a new AzLA Special Interest Group. The eResource group proposes to plan and promote ways to learn about and share content-based online resources, including databases, ebooks and related content.
• To share information on new and model e-content projects, platforms and tools, including both locally developed and commercially purchased.
• To share information on statewide e-content projects.
• To work together to develop resources to enhance the library users' online experience.
• To further working relationships between all types of libraries around e-content.
• Host an annual, day-long eResources forum. The forum will include presentations and panels on research, trends, issues and the future of digital libraries.
• Host two webinars showcasing new e-content projects.
• Organize and sponsor an annual program at the AzLA conference, and hold an annual business meeting at the conference.
• Share information in the AzLA newsletter and through a listserv.
• Host quarterly Interest Group Council and Planning Meetings, which are open to all members.
To get started, we need to recruit at least 25 charter members, and officers – chair, vice chair, immediate past chair and recorder. As this is an AzLA group, members and officers need to be AzLA members.
If you'd like to be a charter member, are willing to be an officer, or would just like more information, contact Laura Stone, Digital Content Director, Arizona State Library, Archives and Public Records, a division of the Arizona Secretary of State by email at lstone@azlibrary.gov or phone, 602-926-3469.


You are currently browsing the tag archive for the 'Confirmation' tag.
Here are my sermons from our Sunday morning services for the Proper 17, the twelvth Sunday after Pentecost. You can find the track 1 lectionary readings for the day HERE.
8:30 Service, in which we explore power, anger, and grief.
10:00 Service, which we explore the sacrament of Confirmation and rites of passage.


text:
Home News Ocean New Zealand rescued 28 stranded whales, fifteen died
New Zealand rescued 28 stranded whales, fifteen died
A beached whale at Farewell Spit in New Zealand, photo: Marion Sutton/Reuters
Rescuers successfully refloated 28 pilot whales stranded on a beach in New Zealand on Tuesday, but the animals remained close to shore and could beach themselves again, wildlife officials said.
"While the whales have come close to shore at times, they remain free-swimming," whale conservation charity Project Jonah New Zealand said on its Facebook page. They'll keep monitoring the animals to make sure they don't strand again.
The Department of Conservation (DOC) said the pod of long-finned pilot whales was seen beached early Monday at Farewell Spit. Around 60 volunteers worked around the clock to save them.
"The whales have been close to shore and it's uncertain whether they will swim off or possibly re-strand," a DOC spokesperson said. "DOC rangers and volunteers remain on-site ready to respond if the whales start swimming for shore and become stranded again."
Farewell Spit is a narrow sand point at the northern end of the Golden Bay on South Island, the biggest of the two major islands of New Zealand. In the past fifteen years, at least ten pilot whale strandings have happened there.
The most recent was in February 2017, when almost 700 of the marine mammals beached, resulting in 250 deaths. In November, about 100 pilot whales died in a mass stranding on New Zealand's remote Chatham Islands.
Mass strandings remain a mystery
New Zealand and neighbouring Australia are hotspots for mass whale strandings. Marine biologists don't know why the stranding happen.
Some researchers think that pilot whales can go off track after being attracted by food close to the shoreline, or sometimes they follow a leader or gather around an injured or distressed whale.
Olaf Meynecke, a whale researcher at Australia's Griffith University, said pilot whales use sophisticated sonar to find prey and for orientation, so some theories link strandings to changes in electromagnetic fields.
"These changes can be caused by solar storms or earthquakes (seismic activities), but there is also a strong connection between active sonar, for example naval sonar, and dolphin strandings, including pilot whales," Meynecke said.
The biggest beaching in modern history was recorded in Australia, also last year, when almost 470 pilot whales died after beaching themselves on the country's remote southern coast.
The Animal Reader wants to encourage people to question whether it's ethically and morally correct to treat animals the way we do in our society. We do this by reporting on news about animal welfare. If you can, please consider supporting animal journalism.
pilot whales
Previous articleIsrael's beaches covered with tar after oil spill, killing turtles
Next articleDavid Attenborough to UN: 'Climate change a threat to global security"

redpajama_set_name: RedPajamaCommonCrawl


Qstream combines mobile, science and gamification in a powerfully simple solution that's helping today's healthcare leaders reinforce the knowledge and skills that matter most.
Developed at Harvard Medical School, Qstream engages your clinicians in fun, challenge competitions they enjoy – and delivers the real-time insights that supervisors depend on – to ensure patient safety, and more.
Built for Busy Healthcare Professionals. Qstream is built for the way that clinicians work. Using our native mobile apps or Webmail, Qstream takes only minutes a day, is non-disruptive to work time and ensures that the knowledge and skills that matter most will stick. With 94% average engagement rates, clinicians prefer it!
Clinically Proven. Qstream is the only solution whose effectiveness has been clinically proven in rigorous scientific trials to enhance on-the-job performance and durably change behaviors with impact to patient outcomes – by letting clinicians play a "game" on the their phone or tablet in minutes a day.
Fast and Easy to Use. Delivered from the cloud to any mobile device, the award-winning Qstream platform is easy to use and deploy at scale. With all the security and reliability that IT demands, Qstream integrates seamlessly with third-party information systems and is available out-of-the-box in 15 languages.
Measurable. Qstream's next-generation reporting and analytics engine instantly and continuously synthesize millions of data points into real-time "heat maps" and targeted improvement actions that ensure readiness and maximize the effectiveness of your CME investments.
Trusted by Leaders in Healthcare. Qstream is used by 13 of the top 15 pharmaceutical firms, numerous life sciences companies, leading medical centers and teaching schools to improve quality of care and patient outcomes.


text:
O Sultanato de Agadez (também conhecido como Tenere Sultanato de Aïr, Sultanato de Aïr, ou Asben) foi um reino berbere centrado na cidade de Agadez nas Montanhas Aïr, localizado na borda sul do deserto do Saara, no centro-norte do Níger, no continente africano. Foi fundada em 1449, pelos povos Tuareg e Hausa como um posto comercial. O Sultanato de Agadez foi posteriormente conquistado pelo Império Songhai em 1500. Após a derrota do reino de Songhai, em 1591, o Sultanato de Agadez recuperou sua independência. Ele experimentou um declínio acentuado na população e na atividade econômica durante o século XVII. O reino foi posteriormente conquistado pelos franceses, em 1900.

Dinastias berberes
Estados extintos da África da Idade Moderna
História do Níger
Região de Agadez

redpajama_set_name: RedPajamaWikipedia


Exceptional Upper Level, End Unit in Gated Sunpointe Condos in prime location opens to nice park-like area w/shade trees, quietly tucked away from I-5 & entrance. NEW HVAC June 2018! Kitchen Updated w/Granite Tile Counters, Appliances & Cabinets! Custom opening to Living Room from Kitchen across Granite topped Dining Bar (unique!). Step out onto Balcony from Living Room & enjoy the peaceful view and pleasant Delta breezes! Beautiful Tile & Laminate Flooring in Entry, Living Room, Kitchen & Baths. Master Suite has 2 Double Closets & NEW Shower Stall! Bathrooms were both updated! Designated, Covered Carport is just steps in front of staircase. Laundry Room is close and so are the 2 Pools, Clubhouse, Rec Facilities, Sauna & Spa. Tennis Courts in back. Water & Trash incl in HOAs. Near I-5, Delta College, UOP, Bus Stop, Park, Shopping, Restaurants, more!


A refurbishment and roof extension to a Grade II listed terrace dwelling in South Kensington, London. The formal façade remains unaltered at fourth + fifth floor, but the interior was entirely renovated creating bright minimal spaces through a sensitive dialogue with historic details.
The proposal is to reconfigure the existing rear roof form to follow the original roof profile retained by the majority of the terrace.
This creates usable space within the roof space (5th floor) to create a master bedroom with ensuite and two additional bedrooms, one with an ensuite and the other opening onto an external roof terrace. The proposal also looks to reconfigure the 4th floor layout to provide more spacious kitchen, bathroom, dining room and living room.
The new roof is a sympathetic addition to the row of Victorian terrace dwellings, with a traditional mansard form clad in slate and pierced with lead dormers. Internally, at fifth floor level, the views are framed by the existing refurbished stone balusters towards the Natural History Museum.
At the rear the water tank room at roof level was removed and a roof terrace created that faces west onto Queen's Gate Place Mews, enclosed by a contemporary balustrade design.


Check MAIDS Senior Resident Result 2019, which was released by the board of the Maulana Azad Institute of Dental Sciences on the date of the 08th April 2019 at the official website @ www.maids.ac.in. So, candidates without any delay download the MAIDS Senior Resident Merit List and check out the marks of the written examination.
By just refer the whole page, candidates can get the whole details about the MAIDS Dental Specialist Result. So, applicants who have attempted the written examination on the 06th April 2019, those ones just click on the mentioned link on the below page and get the MAIDS Senior Resident Answer Keys of the exam along with the MAIDS Senior Resident Cut Off Marks.
To reduce the tension about the marks of the written examination, the officials have declared the MAIDS Dental Specialist Result for the sake of all the written exam takers. So, postulants who are looking for the marks of the written examination, those ones refer mentioned link on the below page @ www.jobschat.in and check the MAIDS Senior Resident Result 2019. After checking the result, candidates if you are qualified in the written examination then must take the copy of the www.maids.ac.in Result, which may be necessary for the further rounds of the selection process i.e Interview Round.
After the written exam completion very few days, the Maulana Azad Institute of Dental Sciences Officials has released the MAIDS Dental Specialist Answer Keys of the written examination. Because based on that Answer keys only, the all the written exam takers can assume the marks of the written examination. So, contenders without any late click on the highlighted link on the below table and get the set-wise MAIDS Senior Resident Answer Keys. After that, candidates check it with the correct set among all the sets and also which set you have attempted in the examination hall.
Along with the MAIDS Senior Resident Result 2019, the Cut Off Marks also released. So, candidates refer the provided pdf on the below page and get the clarity about the MAIDS Dental Specialists Cut Off Marks of the written examination. Based on the cut off marks only, the officials filter some of the candidates to the interview round. So, candidates check out the MAIDS Senior Resident Cut Off Marks of the written examination, which may useful for you. Finally, candidates don't forget to check out the marks of the written examination with the help of the mentioned links.
On the date of the 08th April 2019, the board of the MAIDS has published the MAIDS Dental Specialist Merit List on their respective sites. For the sake of all the visitors, we have uploaded the MAIDS Senior Resident Merit List on this web page. So, candidates who are willing to check the marks of the written examination and also know if you are qualified for the interview round, then without any delay download the www.maids.ac.in Senior Resident Merit List and check it with the application number and your name, the links are mentioned on the below table.


Categories: Hampers, Oils and Vinegars.
further maturing for at least one year. Aging in wood gives the product an amber colour and improve the organoleptic flavours as tannins.
Terre Bormane Hazelnut Oil is obtain by cold pressing hazelnuts from Piedmont Italy. It has a sweet flavour; ideal for all types of salads, in particular with bitter salads (chicory, endive, etc.). ideal for pastry.
This oil is bursting with fruity and fresh lemon flavours – it's ideal to use in salad dressings, as a dipping oil or to drizzle on grilled seafood or sashimi. It's made by crushing olives and fresh lemons together, then draining off the water and juice to leave behind the richly-scented extra virgin olive and citrus oil blend. Keep a bottle in your pantry to liven up your favourite dishes, it also makes a great foodie present. 500ml bottle.
This oil is from producer Casa Olearia, based in the heart of the Ligurian Riviera – a region known for producing high quality extra virgin olive oils.
This EVOO is made from a special selection of olives, collected from the olive grove of Roi- Morga in Montalto Ligure, 250 meters above sea level. The olives are selected when 20% are green, 50% are undergoing maturation and 30% are mature. Tones of dried fruit and an aroma of green apple peel enrich this sweet oil.
Located in the Valley Argentina, Linguria Italy, the Boeri family has been producing Olive Oils only from Taggiasca Olives for four generations. Using traditional techniques, the olives are gently cold pressed using a granite millstone. D.O.P certified.
This is one of the finest oils in the Terre Bormane range. It's an unfiltered, aromatic, extra virgin olive oil with a well-developed fruity taste. From producer Casa Olearia, based in the heart of the Ligurian Riviera – a region known for producing high quality extra virgin olive oils.
Balsamic Vinegar from farmhouse producer Acetaia Reale in Modena, Italy. 'Serie 10' means it has been matured over time in a series of 10 wooden barrels (approximately 10 years), creating a a rich, sweet/savoury flavour. Ideal to serve with grilled fish and roasted meats, bresaola, aged cheeses, vanilla ice cream and fruit salads. 250ml bottle in box.
This Balsamic Vinegar of Modena is obtained from the slow fermentation of cooked musts from grapes of the area of origin appropriately mixed with aliquots of strong wine vinegar. Naturally aged in small wooden barrels of giving various essences such as the oak, chestnut, mulberry, etc. A pantry essential.
'A very mild and bright October day with a brilliant clear sky.' Like all early produce, Ottobrata is highly anticipated – it's the first extra virgin oil of the season, made from olives picked early at the beginning of October. With its unmistakable intense, lively and redolent aroma, and unique flavour it's highly sought after by olive oil enthusiasts. From producer Casa Olearia, based in the heart of the Ligurian Riviera – a region producing some of the finest olive oils in the world. 500ml bottle.
Classic balsamic vinegar from farmhouse producer Acetaia Reale in Modena, Italy. A kitchen staple ideal for use in dressings and marinades. 250ml bottle.


Photo: Shutterstock An estimated 26.9 million American adults have some type of visual impairment, from "trouble seeing" to complete blindness, according to a 2017 National Health Interview Survey. With the aging Baby Boomer generation, this population is expected to grow.
After receiving orientation and mobility training, people with vision impairment can usually travel independently to known places along familiar routes by relying on a white cane or a guide dog to avoid obstacles. However, neither of these provides spatial awareness along their path (information to help them perceive the presence of a work zone, traffic intersection, bus stop, or subway entrance, for example) or guidance information to a destination.
For Chen-Fu Liao, a senior research associate in the U of M's Department of Mechanical Engineering, technology offers the potential to revolutionize the way people with vision impairment navigate city streets. In previous work, Liao developed the Mobile Accessible Pedestrian System (MAPS), which uses smartphone technology to provide location, signal timing, and work-zone information to visually impaired pedestrians. Developed in collaboration with Minnesota's Vision Loss Resources, MAPS received positive feedback from testers. However, Liao discovered the technology was not acceptably reliable in GPS-unfriendly areas.
In his latest project, sponsored by the Roadway Safety Institute, Liao is aiming to improve the app's accuracy and reliability by developing a "self-aware" infrastructure—one that can monitor itself and ensure the information it's providing is up to date, even in urban canyons or indoor environments. To that end, Liao and his team have developed a standalone Bluetooth Low Energy (BLE) smart system integrating commercial off-the-shelf BLE beacons.
First, the researchers integrated the beacons with the necessary interface elements to sense other BLE devices within their range, Liao explains. The BLE beacons can be attached to traffic signal poles, work-zone barrels, or other objects and placed at decision points such as bus stops or building entrances. Then, using a positioning and mapping algorithm, the system can estimate a user's location based on nearby Bluetooth signals, share information among devices, and inform the system administrator if any beacon location has changed. A database containing the location and message of each device is then integrated with the smartphone app to provide navigation information.
Results of testing in a variety of environments indicate that the system can successfully detect if the location of one or multiple BLE beacons in a network has changed and detect when any of its beacons are not functioning—resulting from a loss of power or vandalism, for example.
Liao has received additional funding from the Minnesota Department of Transportation to deploy the system at six intersections in Stillwater, MN, in the summer of 2019. Researchers will integrate the Bluetooth system with the smartphone app and then conduct real-world tests of the new technology. The University of Minnesota has also filed a provisional patent on the technology.
"The benefit of our approach is that the visually impaired need nothing more than a smartphone with a text-to-speech capability to receive traffic and location information," Liao says.


Many people in the St Leonard's Church congregation are engaged in various forms of pastoral care in Watlington working within different local organisations, committees and charities that they belong to.
People who are ill or housebound in Watlington and who would like to receive a visit or Holy Communion should contact us and we will try to arrange this for them.
Together with our friends at Watlington Methodist Church, St Leonard's has a special link with the Sanctuary Care Watlington and District Care Home. We hold a Service of Holy Communion at the Care Home once a fortnight and a Songs of Praise Service once a month.
Please do contact any of the clergy (details on the "Ministry Team" and "Contact Us" pages) if you have a pastoral need to discuss.


text:
https://apnews.com/article/46fe93b6f5a540adbe842406a7799b80
Will Hurd
Rep. Hurd says US isn't prepared to combat altered videos
May 26, 2019 GMT
FILE - In this May 23, 2019 file photo, Speaker of the House Nancy Pelosi, D-Calif., meets with reporters at the Capitol in Washington. An altered video claiming to show Pelosi slurring her words during a Center for American Progress event in which she said President Donald Trump is obstructing justice is circulating widely across social media platforms. Associated Press journalists who analyzed the false video, and compared it to C-SPAN footage, said its speed had been slowed down by several seconds. AP journalists who monitored the event also said Pelosi appeared coherent throughout the Wednesday event, held in Washington. (AP Photo/J. Scott Applewhite)
WASHINGTON (AP) — A Republican congressman and former CIA officer says America isn't prepared for disinformation campaigns that use altered video to spread false information across social media.
Texas Rep. Will Hurd's comments come days after an altered video giving the false impression that House Speaker Nancy Pelosi was slurring her words spread widely online.
Associated Press journalists did a side-by-side comparison of the false video to C-SPAN footage of Pelosi's speech at a conference in Washington and concluded the altered video had been slowed down.
Hurd also raised concerns on CBS's "Face the Nation" about "deepfake" videos that use artificial intelligence to create realistic-looking videos of real people saying things they've never said.
He says government leaders don't fully understand how the technology could be used in the future.


text:
<?PHP
	/**
	 * draft year view.
	 *
	 * through ajax will display the results of the given year's draft
	 */
	//d($this->_ci_cached_vars);
?>

<?
	function create_draft_table($selections,$viewer_team_id) {

		//create the outer container of the table first
		?>

                    	Rd
                        Pick
                        Team
                        Player

		<?

		foreach($selections as $pick_number => $data_array){

			if($data_array['original_owner']!=$data_array['team_id']){
				$traded = '';
			}
			else {
				$traded = '';
			}
			//create the display table
			$alert="";
			if($data_array['team_id']==$viewer_team_id){
				$alert="alert alert-info";
			}

			echo '
';
				echo '';
					echo ''.$data_array['round'].'';
				echo '	';
				echo '';
				  	echo ''.$pick_number.'';
				echo '	';
				echo '';
				  	echo ''.$data_array['team_name'].$traded.'';
				echo '	';
				echo '';
					if($data_array['fffl_player_id']){
						echo ''.player_name_link($data_array['fffl_player_id'],TRUE,FALSE).'';
					}
				echo '	';

			echo '
';

		}//end foreach of each individual player's row

		//close table container
		?>

		<?
	}
?>

<? echo $year; ?> Drafts

League Draft

Go to: Supplemental Draft

Supplemental Draft

Go to: League Draft

                <button class="btn btn-default dropdown-toggle" type="button" id="team_dropdown" data-toggle="dropdown" aria-haspopup="true" aria-expanded="true">
                    Select Team

                </button>

                   <?
                       foreach($all_teams_id_name as $team_id_ => $name){//team_id is already used for the viewer; added _ to differentiate
                            echo '
'.$name.'
';

                       }
                    ?>

        <? foreach($draft_picks_array['Common'] as $selections){ ?>

                            <? echo date('D M j, g A', $selections['start_time']);?>

                    <?
                        create_draft_table($selections['picks'],$team_id);
                    ?>

        <? } ?>

        <? foreach($draft_picks_array['Supplemental'] as $selections){ ?>

                            <? echo date('D M j, g A', $selections['start_time']);?>

                    <?
                        create_draft_table($selections['picks'],$team_id);
                    ?>

        <? } ?>

<?PHP
/*End of file login.php*/
/*Location: ./application/veiws/Account/login.php*/

redpajama_set_name: RedPajamaGithub


Beginning this spring, the Law Society will be promoting the Lawyer and Paralegal Directory.
To update your information, log in to your Law Society Portal account at portal.lso.ca and select 'Directory'.
Ce printemps, le Barreau fera la promotion du Répertoire des avocat(e)s et des parajuristes.


text:
Q: Full example of nginx configuration file for a localhost on OSX 10.9.2 I installed the nginx 1.4.6, mysql 5.6.16 and php 5.6.0-alpha.2 on a OSX 10.9.2 using homebrew and used the default nginx.conf file and changed the parameters to setup a virtual host. However, I received different types of errors from yesterday and changed the config file many times, but end of with nothing :). Below is the information from my terminal using nginx -V:
nginx version: nginx/1.4.6
TLS SNI support enabled
configure arguments: --prefix=/usr/local/Cellar/nginx/1.4.6 --with-http_ssl_module --with-pcre --with-ipv6 --sbin-path=/usr/local/Cellar/nginx/1.4.6/bin/nginx --with-cc-opt='-I/usr/local/Cellar/pcre/8.34/include -I/usr/local/Cellar/openssl/1.0.1f/include' --with-ld-opt='-L/usr/local/Cellar/pcre/8.34/lib -L/usr/local/Cellar/openssl/1.0.1f/lib' --conf-path=/usr/local/etc/nginx/nginx.conf --pid-path=/usr/local/var/run/nginx.pid --lock-path=/usr/local/var/run/nginx.lock --http-client-body-temp-path=/usr/local/var/run/nginx/client_body_temp --http-proxy-temp-path=/usr/local/var/run/nginx/proxy_temp --http-fastcgi-temp-path=/usr/local/var/run/nginx/fastcgi_temp --http-uwsgi-temp-path=/usr/local/var/run/nginx/uwsgi_temp --http-scgi-temp-path=/usr/local/var/run/nginx/scgi_temp --http-log-path=/usr/local/var/log/nginx/access.log --error-log-path=/usr/local/var/log/nginx/error.log --with-http_gzip_static_module
I would be very appreciative if you can send a full example of nginx.conf file to solve this problem.

A: Below you can find the code that finally worked for three different websites on ports 80, 90 and 100.

user  nobody;
worker_processes  1;
error_log /usr/local/Cellar/nginx/1.4.6/logs/error.log;
pid       /usr/local/Cellar/nginx/1.4.6/logs/nginx.pid;

events {
    worker_connections  1024;
}

http {
    include       /usr/local/etc/nginx/mime.types;
    include       /usr/local/etc/nginx/fastcgi.conf;
    default_type  application/octet-stream;
    access_log    /usr/local/var/log/nginx/access.log;

    sendfile        on;
    tcp_nopush     on;
    keepalive_timeout  65;
    gzip  on;
    server {
        listen       80;
        server_name  localhost;
        access_log  /usr/local/Cellar/nginx/1.4.6/logs/localhost.access.log  combined;

        location / {
            root   /Users/apia/Websites/jackpot;
            index  index.html index.htm index.php;
        }
        location ~ \.php$ {
            root           /Users/apia/Websites/jackpot;
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_index  index.php;
            fastcgi_param SCRIPT_FILENAME /Users/apia/Websites/jackpot$fastcgi_script_name;
            include        /usr/local/etc/nginx/fastcgi_params;
        }
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }
    }
    server {
        listen       90;
        server_name  localhost;
        access_log  /usr/local/Cellar/nginx/1.4.6/logs/localhost.access.log  combined;

        location / {
            root   /Users/apia/Websites/fiftyfirst;
            index  index.html index.htm index.php;
        }
        location ~ \.php$ {
            root           /Users/apia/Websites/fiftyfirst;
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_index  index.php;
            fastcgi_param SCRIPT_FILENAME /Users/apia/Websites/fiftyfirst$fastcgi_script_name;
            include        /usr/local/etc/nginx/fastcgi_params;
        }
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }
    }
    server {
        listen       100;
        server_name  localhost;
        access_log  /usr/local/Cellar/nginx/1.4.6/logs/localhost.access.log  combined;

        location / {
            root   /Users/apia/Websites/sunshine;
            index  index.html index.htm index.php;
        }
        location ~ \.php$ {
            root           /Users/apia/Websites/sunshine;
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_index  index.php;
            fastcgi_param SCRIPT_FILENAME /Users/apia/Websites/sunshine$fastcgi_script_name;
            include        /usr/local/etc/nginx/fastcgi_params;
        }
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   html;
        }
    }
}

redpajama_set_name: RedPajamaStackExchange


Whether it's the Take That comeback tour or Tom Jones, Alan B'Stard or Cats book a ticket to see your favourite band and shows and you can pay half as much again for the privilege. Fees of £15-£20 on top of the ticket price are not uncommon.
So I thought I'd tap MoneySavers' huge wealth of knowledge to share tried and tested methods to help cut the cost of booking tickets to concerts, shows and exhibitions.
Last edited by MSE Archna; 25-04-2006 at 2:29 PM.
we have a royalties gold account with the royal bank of scotland that costs £12.00 per month, there are several benefits including 25% discount with no booking fees for theatre or concert tickets, you can purchase 4 at a time, so 4 westend best seats are £55.00 x 4 = £220, with royalties you would pay £165.00 with free delivery and no booking fee.
Living in the midlands I often have a choice of venues for any given tour.
I've found it pays to always search for the venue's own website rather than going through an agency. The best venues are those which maintain there own box office rather than outsourcing it to a seperate company.
For example I saw Rufus Wainwright at the Birmingham Symphony Hall which only charge £1 for postage and no booking fee. This was a saving of £4-£5 over the same concert at Manchester Apollo where tickets have to be bought through an agency.
The thing which really annoys me is when you're initially quoted a ticket price, the next page adds a booking fee and then the final page will add a further "service charge". Surely any admin or postage charge should be absorbed within a single booking fee per ticket?
Anyone who is a fan of show/events/live bands that take place at London's Astoria or Kentish Town's Forum venue can pay £0 booking fees and £0 delivery by buying the tickets in person from the Astoria box office.
At the Astoria box office I purchased tickets for 2 gigs, one for the Astoria, one for the Forum, saving myself £3.50 per ticket on booking fee and a £5 delivery charge. If I had booked these online I would have paid an extra £17 if I had booked them through the biggest internet ticket retailer.
Obviously this is only of benefit to those who live in London, but it beats paying those extra fees!.
I agree. The likes of Ticketmaster I find particularly galling. They charge at least £1.50 postage, yet it's a second class stamp and they stuff the envelope full of third-party advertising. They should be paying *us* for posting this trash. As a result I haven't bought a single ticket from Ticketmaster for over three years now. If I see something I want to go to and it's only available through Ticketmaster, I don't go.
For booking, I've found Express Events to be excellent: hard-to-find tickets at excellent prices and usually no extras over the face value. Often less than face-value.
For Arsenal tickets (come on you Gunners), I use Ticketmaster's Web site to see what tickets are available and then call or write to the stadium to buy them, saving several pounds per ticket.
This has been a bugbear of mine for a long time, so I'm very grateful that MSE is covering it at last.
I echo this. Buying from the venue directly if the best way to get the lowest booking fee. Concert promoters themselves generally don't sell tickets directly, although you could try this is you know who they are.
I regularly go to the Birmingham Academy - buying tickets through their own website generally saves money on the booking fee compared to the likes of Ticketmaster.
One other tip on concert ticket sales - if a show is listed as SOLD OUT, it might not be! When a gig goes on sale, the promoters often hold a fixed allocation for the record company/band/support band to buy tickets for guests from. If the record company/band/support band don't buy them all, the excess will be released through certain ticket agents at a later date. So, if you contact the concert PROMOTER when a show is listed as sold out, and ask them if there are any record company holds, and could you get added to a waiting list for any returns?, you might get lucky! If the show recently went on sale and sold out quickly, you might get lucky! If the show sold out ages ago, its less likely... no guarantees.
Never thought of contacting the promoter directly, so will try that one!
I live in Preston and most of the gigs i go to are in Manchester so I have to use agencies. If you do buy tickets direct from the box office or another outlet do you just pay the face value of the ticket or do you have to pay admin/booking/cc charge?
I agree. The likes of Ticketmaster I find particularly galling. They charge at least £1.50 postage, yet it's a second class stamp and they stuff the envelope full of third-party advertising. They should be paying *us* for posting this trash.
I hate ticketmasters policy, charging around £3.50 for EACH ticket and then £1.50/£2 for postage, even if you want to pick them up from the venue!
I went to find out about tickets to see Little Britain in Cardiff for 4 and all the extra charges were adding about £16 to the total amount. In the end I went in person to the CIA Box Office in Cardiff and bought with cash (as they still wanted to charge £3.50 per ticket even with a Debit Card). The only annoying thing about this was that when the event was postponed and then cancelled, I had to take the tickets back in person to get a refund!
What annoys me is that all these charges should be in the ticket price in the first place (well maybe not for postage but they shouldn't charge for you to pick them up)!
One other tip on concert ticket sales - if a show is listed as SOLD OUT, it might not be!
Remember also that each ticket agency often has its own allocation of tickets, so if one agent has sold out other agents might still have some left. You should also shop around - different agents charge different fees for the same tickets and it can also vary from show to show.
If you want cheap tickets (eg in the gods) then you might need to shop around there as well because some agents don't sell the complete range of tickets or might have sold their allocation of the cheaper ones.
Bear in mind that some venues' own box offices are linked to an agency - if I phone the lady on the desk at the Grand Opera House in York it is charged through Ticketmaster with all the fees but if I go in and buy from the same lady in person there are no fees!
Last edited by MSE Jenny; 28-04-2006 at 3:00 PM.
Dont go on the NEC website. Trying to buy George Michael tickets on sunday at 10 am. By 30 seconds past 10 am the web site had crashed.
I also know the owner of Capital Sound, (Not Capital Radio). Although I have not tapped him up for tickets yet. Perhaps a back stage pass at one of Kylies next gigs if she does another.
(2) Check local independent record shops for tickets for the smaller bands - eg here in Nottingham, Selectadisc Records sell tickets for Rock City/Rescue Rooms with a minimal booking charge of about 50p, if that.
(3) Blag a free ticket - if the group has an official website try contacting them and say you'll write a full review. Alternatively try one of the online or paper music magazines or, better still, your local newspaper : chances are they can get you on the guest list in return for a written review and maybe some photos. MInd you, this is unlikely to work for big names, only smaller bands.
Nat West also offer 25% discount on event and theatre tickets through their Advantage Premier account. This costs £14.95 per month, and offers many other benefits. I have used the service a few times, and it works perfectly.
Sometimes shows are on sale through more than one agency with hugely different booking fees. For smaller music shows, try wegottickets.com - they charge the lowest booking fee by far (max 10% and often less) AND there's no postage as all tickets are electronic - no junk mail either. They don't have that many shows yet, but getting more all the time.
...This was a saving of £4-£5 over the same concert at Manchester Apollo where tickets have to be bought through an agency.
Living in the Midlands, this probably doesn't help you, but tickets for the Manchester Apollo can be bought without booking fees by going to the booking office at the Palace Theatre, since it forms part of the same group.
I'd echo what others have said: if you can get to the venue ticket office, there are usually no additional charges (for cash), and indie record shops also do good deals. If you are going to the type of gig that indie shops support, you can usually pay on the door for about a quid extra which won't help you get tickets for stadia tours, but should help out for small bands on the up.
I wanted to see Lion King and after searching many ticket sites i decided when i was in london one day to go along to the theatre itself. I'm glad i did, not only was there no booking fee but I could also choose from their seating plan where we sat but the best bit was that i got a price reduction because my sister is registered disabled. i didnt need to bring the blue badge and didnt need to bring it on the night to prove i had it. Her ticket was approx half price! When i enquired about this originally over the phone and on web sites there was no offer of a price reduction.
Also then got to take all the tickets home with me and not pay another high postage charge!
would def goin person again but realise this isnt always possible!
I rarely use ticket agents for London Theatre - the National Theatre, Royal Opera House and many others let you buy online or by phone at Box office prices with no booking fee and no more than a £1 charge for postage - which you can avoid by picking up tickets on the day.
It can be hard to find box office websites online, because a Google search will usually come up with a massive list of agents for any given theatre/play - but I have built up a list of 'favourites' by always asking for website details & asking to be added to the mailing list whenever I ring a box office to book tickets for a particular play, ballet or whatever.
Oh my God! Have I really just seen a post where the writer has actually used an apostrophe - and correctly? Sorry if this doesn't follow the thread but it is so unusual I just had to comment!
www.seeticekts.com – These guys tend to get most gigs and there website always dies when a large event goes on sale.
B)	Where possibly always go for venue pick up option . This can save you £5 per order . For this reason if ticektweb are doing the event then these guys are my personal favourite. Seetickets ( who also have a site under gigsandtours.com) don't offer venue pickup unless the event is in the next few days and postage wouldn't be possible . The best thing to do is book the ticket online . Ring them up, you can use this number 01159 454590 which will go straight to their customer serve team and you can request venue pick up as an option and they will refund the delivery. If customer services is busy or closed you will go through to their call canter and you will need to request a customer service call back for this to be done . The call centre can be very unhelpful however insist you want venue pick up and insist you want customer service to refund the delivery and they will call you back. I have as yet been unable to do this with ticketmaster but I am sure with a bit of persistence it can be done to.
C) By far the best and cheapest way or them all is where and when possibly if you can go either directly to the ticket outlet or venue buying the tickets without booking fees and charges. The only let down is they normally only take cash and no credit cards.
Using the above methods I save at least £20 a month in booking fees and postage charges . I hope you all can benefit from the above.
Last edited by MSE Jenny; 28-04-2006 at 2:10 PM.
Also, check www.lastminute.com who get an allocation on most theatre and music events, with varying booking fees. These fees are transaction fees which include postage on gig tickets.
They sold first reserve George Michael tickets for a total of just over £67 including fees, where other sites were offering the same for about £100.


text:
MiFID - Secondary Markets X Planning reporting budget X Post Trading X European Single Electronic Format X Audit X Risk Analysis & Economics - Markets Infrastructure Investors X Market Integrity X Technical Advice X Q&A X
05/11/2020 ESMA74-362-893 QAs on SFTR data reporting Post Trading, Securities Financing Transactions, Trade Repositories Q&A PDF
08/07/2020 ESMA70-1861941480-52 Q&A on EMIR implementation Post Trading Q&A PDF
08/07/2020 ESMA70-1861941480-56 Q&A on MiFIR data reporting MiFID - Secondary Markets, Supervisory convergence Q&A PDF
08/07/2020 ESMA70-708036281-2 Q&As- Central Securities Depositories Regulation Post Trading Q&A PDF
29/05/2020 ESMA70-872942901-35 Q&A on MiFID II and MiFIR transparency topics MiFID - Secondary Markets Q&A PDF
29/05/2020 ESMA70-872942901-38 Q&A on MiFID II and MiFIR market structures topics MiFID - Secondary Markets Q&A PDF
01/04/2020 ESMA70-156-2287 Technical Advice to the European Commission on weekly position reports under MiFID II MiFID - Secondary Markets, Supervisory convergence Technical Advice PDF
17/02/2020 ESMA70-708036281-2 Questions and Answers on CSDR Post Trading, Supervisory convergence Q&A PDF
29/03/2019 ESMA70-145-111 Q&A on the Market Abuse Regulation Market Abuse, Market Integrity Q&A PDF
The purpose of this document is to promote common supervisory approaches and practices in the application of MAR and its implementing measures. It does this by providing responses to questions posed by the general public and competent authorities in relation to the practical application of the MAR framework
The content of this document is aimed at competent authorities to ensure that in their supervisory activities and their actions are converging along the lines of the responses adopted by ESMA and at helping issuers, investors and other market participants by providing clarity on the content of the market abuse rules, rather than creating an extra layer of requirements.
27/03/2019 ESMA70-872942901-36 Q&A on MiFID II and MiFIR commodity derivatives topics MiFID - Secondary Markets Q&A PDF
02/02/2018 ESMA70-151-1179 Questions and Answers ESMA CCP Stress Test Post Trading Q&A PDF
14/12/2017 ESMA70-151-957 MiFID II Q&A on post-trading issues MiFID - Secondary Markets, Post Trading Q&A PDF
29/04/2016 2016/665 Q&A on ESMA's EU-wide stress tests for CCPs Post Trading Q&A PDF
05/08/2015 2015/1219 Final Report- Technical Advice under the CSD Regulation Post Trading Technical Advice PDF
19/12/2014 2014/1569 Technical Advice to the Commission on MiFID II and MiFIR MiFID - Investor Protection, MiFID - Secondary Markets Technical Advice PDF
2.8 MB Reasons for publication The European Securities and Markets Authority (ESMA) received a formal request (mandate) from the European Commission (Commission) on 23 April 2014 to provide technical advice to assist the Commission on the possible content of the delegated acts required by several provisions of Markets in Financial Instruments Directive (MiFID II) and the Markets in Financial Instruments Regulation (MiFIR). The mandate focuses on technical issues which follow from MiFID II and MiFIR and is available on the European Commission website (here). ESMA was required to provide technical advice by no later than six months after the entry into force of MiFID II and MiFIR (2 July 2014). Contents This final report follows the same structure as the Consultation Paper (CP) published by ESMA on 22 May 2014 which is: (1) Introduction, (2) Investor protection, (3) Transparency, (4) Data publication, (5) Micro-structural issues, (6) Requirements applying on and to trading venues, (7) Commodity derivatives and (8) Portfolio compression. This paper also contains summaries of responses to the CP received by ESMA. The rationale of those items covered already in the CP for which no relevant changes have been introduced, is not developed again in this Final Report. ESMA recommends, therefore, to read this report together with the CP published on 22 May 2014 to have a complete vision of the rationale for ESMA's technical advice. Next steps Delegated acts should be adopted by the Commission so that they enter into application by 30 months following the entry into force of the Directive and Regulation, taking into account the right of the European Parliament and Council to object to a delegated act within 3 months (which can be extended by a further 3 months).
30/01/2014 2014/123 ESMA Technical advice on equivalence of Japan for CCP II- Commodities CCPs Post Trading Technical Advice PDF
ESMA delivers second set of advice on EMIR equivalence Following its technical advice published on 9 September 2013, the European Securities and Market Authority (ESMA) has published a supplement to its advice to the European Commission on the equivalence of the regulatory regime for central counterparties (CCPs) of Japan with the European Markets Infrastructure Regulation (EMIR). This supplement to the September 2013 Final report sets out ESMA's advice to the European Commission is in respect of the equivalence between the Japanese regulatory regime for commodity CCPs and the regulatory regime for CCPs under EMIR. ESMA proposes conditional equivalence As for ESMA's advice to the Commission in respect of Japan for CCPs which clear transactions relating to securities, currencies, interest rates, credit, weather, GDP and other indices, ESMA considers that the Japanese regulatory regime for commodity CCPs contains legal provisions and involves supervision and enforcement similar to that of EMIR. The Commission is expected to use ESMA's technical advice to prepare possible equivalence decisions. Where it adopts such a decision, certain provisions of EMIR may be disapplied in favour of equivalent third-country rules. In particular, ESMA may recognise within the EU a CCP which is authorised outside the EU. The different pieces of advice are available on ESMA's website.


text:
Join Cindy's Newsletter!
Hot Flash Blog
Killer Cocktail Contest
By Cindy Sample | July 9, 2013 | 43
I love holidays – the bigger the spectacle the better. With Sacramento temps hovering at 110 degrees or more this summer, there's nothing like a cool, refreshing libation to kickstart the party spirit. Speaking of cool cocktails and hot celebrations, did you know that July 19th is National Daiquiri Day? I discovered this amazing tidbit…
Dying for a Daiquiri – Uncovered
By Cindy Sample | May 30, 2013 | 88
Congratulations to contest winner Jaci Muzamel. Who knew choosing the cover for a book titled Dying for a Daiquiri would be more controversial than the debate over the location of the Kings' basketball team? After reading the blog and Facebook comments regarding my four diverse cover selections, I have far more sympathy for Congress. And…
The Deadly Daiquiri Cover Up
By Cindy Sample | April 11, 2013 | 363
Congratulations to contest winner Priscilla Caporaletti-Bean. How many of you have taken a Hawaiian vacation, only to discover paradise can be perilous? Sure, those beautiful islands offer balmy breezes, turquoise water, waving palm fronds, and sandy beaches. But what about deadly sharks? Poisonous sea urchins? And the most lethal of them all? Those fruity drinks…
My Dream Date – Fiction vs. Reality
By Cindy Sample | February 6, 2013 | 65
Every year as Valentine's Day approaches, my thoughts turn to romance. Well, to be honest, they turn to chocolate then to romance. As a single woman, and card-carrying member of the AARP, what are my expectations for the love interest in my life? I used to go for the tall, dark, silent type but lately…
The Popsicle Syndrome
By Cindy Sample | January 30, 2013 | 20
Written by Guest Blogger Terry Ambrose Today I welcome Terry Ambrose, author of two very funny mystery series. Terry and his protagonists seem to have something in common. Find out if you do as well. •••••••••••••••••••••••••••••••••••••••••• It's not easy being a smart ass. There are days when it's as simple as falling off a paddleboard.…
You Don't Know Jersey
Written by Guest Blogger Lois Winston It's my pleasure to introduce my Guest blogger today, award-winning romance and mystery author, Lois Winston. If you've watched Jersey Shore or read about New Jersey in Janet Evanovich's Stephanie Plum series, you may think you know all about it. But according to Lois: •••••••••••••••••••••••••••••••••••••••••• I live in…
Death By Spanx
By Cindy Sample | January 1, 2013 | 108
Congratulations to contest winner Karen Lange. For those readers who consumed the Fifty Shades of Grey trilogy, please note this blog post is not about a physical relationship which incorporates any form of bondage or discipline. Or is it? I recently had an encounter that left me tormented and imprisoned. I've never felt such anguish…
Trick or Treating Is Not for Sissies
By Cindy Sample | October 30, 2012 | 39
Congratulations to contest winner Cathy Ann Adkins. Written by Guest Blogger Heather Haven I love Halloween. 1. You get to dress up in crazy costumes, even when you're giving speeches at the office! Anyone notice a similarity to the clown costume Laurel wore in DYING FOR A DATE? What detective wouldn't want to smooch with…
Killer Recipes Even a Klutz Can Cook!
By Cindy Sample | October 2, 2012 | 56
Congratulations to contest winner Linda Lovely. There's a nasty rumor going around that I can't cook. I'm not sure where this rumor started, but I'm guessing it began somewhere in my kitchen. Maybe near that burner that ignited the last time I tried to sear a salmon. Possibly it originated in the microwave. Have you…
By Kaye George | September 27, 2012 | 50
Congratulations to contest winner Marilyn Meredith. Written by Guest Blogger Kaye George Today I welcome guest blogger Kaye George. Kaye has been a janitor, a mental health center secretary, a short order cook, a violinist, an online mystery reviewer, and is now an award-winning short story writer, two-time Agatha nominee, and the author of the…
WHO'S YOUR FAVORITE DETECTIVE?
DYING FOR A COVER
DYING FOR SOME TOILET PAPER
HELP ME CHOOSE A CHASE SCENE
AN ODE TO READERS
Cindy Sample on WHO'S YOUR FAVORITE DETECTIVE?
Jana on WHO'S YOUR FAVORITE DETECTIVE?
Copyright © 2023 Cindy Sample. Site by AuthorBytes.


text:
import svelte from 'rollup-plugin-svelte';
import commonjs from '@rollup/plugin-commonjs';
import resolve from '@rollup/plugin-node-resolve';
import replace from '@rollup/plugin-replace';
import livereload from 'rollup-plugin-livereload';
import { terser } from 'rollup-plugin-terser';
import css from 'rollup-plugin-css-only';

const production = !process.env.ROLLUP_WATCH;

function serve() {
	let server;

	function toExit() {
		if (server) server.kill(0);
	}

	return {
		writeBundle() {
			if (server) return;
			server = require('child_process').spawn('npm', ['run', 'dev:sirv', '--', '--dev'], {
				stdio: ['ignore', 'inherit', 'inherit'],
				shell: true
			});

			process.on('SIGTERM', toExit);
			process.on('exit', toExit);
		}
	};
}

export default {
	input: 'src/index.js',
	output: {
		sourcemap: !production,
		format: 'iife',
		name: 'shortcuts',
		dir: production ? '../../docs/rsrc/dist' : 'public/rsrc/dist',
		entryFileNames: production ? 'shortcuts-[hash].js' : 'shortcuts-hash.js',
	},

	plugins: [
		svelte({
			compilerOptions: {
				// enable run-time checks when not in production
				dev: !production
			}
		}),

		css({ output: 'shortcuts-hash.css' }),

		// If you have external dependencies installed from
		// npm, you'll most likely need these plugins. In
		// some cases you'll need additional configuration -
		// consult the documentation for details:
		// https://github.com/rollup/plugins/tree/master/packages/commonjs
		resolve({
			browser: true,
			dedupe: ['svelte']
		}),
		commonjs(),

		replace({
			values: {
      	'process.env.NODE_ENV': JSON.stringify('develepment'),
    	},
			preventAssignment: true
		}),

		// In dev mode, call `npm run start` once
		// the bundle has been generated
		!production && serve(),

		// Watch the `public` directory and refresh the
		// browser on changes when not in production
		!production && livereload('public'),

		// If we're building for production (npm run build
		// instead of npm run dev), minify
		production && terser()
	],
	watch: {
		clearScreen: false
	}
};


This question is how to disable vice call.
I create wirmwware for me MCU with support upgrade firmware over GPRS.
I want use FTP for read data (defined file in server) and upgrade firmware in my MCU.
But if enable FTP still can receive voice call from other cell phone and receive RING string every 5 sec if is incoming call.
is possible to disable this incoming call???
if receive data from ftp server I need 100% certainty that no other data receive only from file .
how can I make it???
No is not working like this. When a GPRS action is in course the serial link is reserved for this activity, FTP data will not be interfered by anything.
Anyway you can barr all incoming calls see AT+CLCK or set with AT+CGCLASS GPRS Mobile Station Class to "CG" – class C in GPRS only mode (GPRS only.
using barring need network operator password .
this is not good way.


DRTYKNKYNASTY69 selena1x jasmin. KellyAdler. littlehottest. Dawn2tight.
RealSexyLoveAliceSteeleAlexaAndDamonDayanaRogers .AmmalyGreynatallyeeAsianHotLULUWestDariya .ZeroBelowAvalonPricelessViolettRosehotmistresxoxcum .JennyKleinAsianHotLULULITTLEBUNNIES4UtYleRTIGER .AliceDianneAvalonPricelesshangelhothardhLITTLEBUNNIES4U .MikeForYouuJennyKleinGoodVibeAssHoleMiaSquirter .MistressMelyssaTeacherIsSexyDominatrix22KellyAdler .OvIdEoCiMabelSinAliceSteeleGoodVibeAssHole .MILKMACHINETSHOTsexyIRENE1Little1MissMILKMACHINETS .ThreeFantasiasDouglasBarnessXa0LovableTwinktYleRTIGER .MistressMelyssaRachellCossNaugthySlaveSlutaBiHottAmazing .
WildHOtMisTRESSTeacherIsSexyprettiesEYES261BabyDoll18 .tYleRTIGERRealSexyLoveMistressMelyssaYourDreamsGirlX .YourDreamsGirlXaBiHottAmazingnatallyeeAvalonPriceless .NaugthySlaveSlutRealSexyLoveAliceSteeleChloeMooree .HOTsexyIRENEMabelSinMichJasscantalia .ViolettRoseAsianHotLULUMILKMACHINETSNaugthySlaveSlut .SpecialMollyAlexaAndDamonLATINNBOYSHOTsexyIRENE .LonnellaAmmalyGreynatallyeeLATINNBOYS .TeacherIsSexyBrightgirllAmmalyGreylittlekinkygirl .raul2youMistressMelyssaJinziWildHOtMisTRESS .WildHOtMisTRESSJaineMichJassThreeFantasias .


text:
Pauline may refer to:

Religion
An adjective referring to St Paul the Apostle or a follower of his doctrines
An adjective referring to St Paul of Thebes, also called St Paul the First Hermit
An adjective referring to the Paulines, various religious orders associated with these two saints, or a member of such an order
Cappella Paolina, or Pauline Chapel, a chapel in the Vatican
Pauline Christianity, the Christianity associated with the beliefs and doctrines espoused by St Paul the Apostle
Pauline epistles, the thirteen or fourteen letters in the New Testament traditionally believed to have been written by St Paul the Apostle
Pauline privilege, a form of dissolution of marriage

People
Pauline (given name), a female given name
Pauline (singer) (born 1988), French singer (full name Pauline Vasseur)
Pauline Kamusewu (born 1982), Swedish singer of Zimbabwean origin, also known as just Pauline

Places
Pauline, Idaho, United States
Pauline, Kansas, United States
Pauline, South Carolina, United States
Pauline, Texas, United States

Other uses
Hurricane Pauline, which devastated much of Mexico in 1997
Pauline (Nintendo), fictional character in the Mario series of video games
Pauline (opera) (1876), by Frederic Cowen
Pauline (chamber opera) (2014), by Tobin Stokes
, an 1839 novel by George Sand
, a United States Navy patrol boat in commission from 1917 to 1919
An adjective referring to St Paul's School, London or a pupil or former pupil of the school
Pauline (crustacean), a fossil genus of ostracods from the Silurian
Pauline avibella, a fossil species
Pauline Laws, the house laws of the Romanov rulers of Russia

See also
Pauleen (disambiguation)
Paulina (disambiguation)
Paulin (disambiguation)
Paulinella, a genus of amoeboids


What is emotional eating and what are the effects?
Emotional eating. The name pretty much sums it up: eating in response to negative emotions like stress, anxiety, sadness, you name it. Anecdotally, it's a pretty common occurrence. If you stood on a street corner surveying passers by, it's likely that most would endorse occasionally raiding the cupboard for something sweet or salty (or both) after a taxing day at the office.
However, in the research world, there are two camps emerging when it comes to emotional eating. In a nutshell, some people think it's a thing, and others think it's not.
Having done a fair bit of research on the topic (see my 2017 article for a full review of the relationship between emotional eating and weight outcomes), I've seen a solid body of evidence to support the validity of emotional eating. When people look at the relationship between emotional eating and weight over time, not surprisingly, they tend to find that emotional eaters gain more weight than non-emotional eaters. Emotional eaters don't just have the tendency to put on weight, they also experience greater difficulties taking it off. In the context of behavioural weight loss interventions (often referred to as RCTs or randomized controlled trials in research), emotional eaters also lose less weight than those who don't engage in emotional eating. And it's not an insignificant amount either. When looking at total weight loss in terms of the percentage of initial body weight lost, emotional eaters lose about 4 per cent less than non-emotional eaters. Given that 5 per cent weight loss is enough to deem it clinically significant, meaning that it helps to reduce the risk for other health concerns like diabetes, heart disease, and other chronic complications, 4 per cent is a pretty big number. With all of this in mind, it's easy to draw the conclusion that emotional eating is not just a "thing" that people do from time to time, but rather a behaviour that has serious implications for long term health and well being.
So despite all of these findings, why do others argue against emotional eating? And what alternative explanation do they provide? Given that the body of literature on emotional eating is vast, the research done on overweight and obese individuals described above is only a subset of all of the studies done in this field. There is also a fairly comprehensive amount of research on normal weight individuals as well. In these studies, normal weight people (which in a standardized sense typically refers to those within a somewhat arbitrary BMI range of 18.5-24.9, although the merits of BMI for describing weight warrant their own article for another day), usually undergraduate university students, partake in laboratory studies looking at emotional eating. Typically, they undergo a mood induction, which involves watching a sad video, or listening to sad music, to put them in a negative mood, and then they are offered a variety of foods to choose from and their consumption is measured. Looking at these types of studies, the findings are mixed as to whether or not negative emotions actually lead to increased food intake.
It's difficult to draw any solid conclusions because researchers in each camp have their arguments against the opposite side. One of the limitations to the normal weight studies is that they are all fairly contrived. Putting someone in a laboratory experiment and observing their behaviour is not necessarily indicative of what you would see in their day-to-day life. That being said, the question still remains as to why some normal weight individuals supposedly engage in emotional eating but still manage to maintain their weight. There are a couple of different theories on this.
One is that normal weight individuals essentially misattribute their overeating to their emotions. Because emotional eating is such a popular social construct, it's easy to eat too much of something and then say, "Oh, I did that because I was super stressed out." There is some evidence to show that when people overeat, they have the tendency to blame it on negative emotions after the fact as an easy out to account for why they ate more than they felt they should have.
Another theory is that normal emotional eaters are just better at self regulating than overweight and obese emotional eaters. They may engage in the exact same behaviour, but do it to a lesser extent and use other mechanisms to cope. For example, they may eat in response to negative emotions, but still stop when they are full, and also do regular exercise to maintain their lifestyle.
Realistically, emotional eating probably falls across a broad spectrum that encompasses all of these explanations. We can draw all of the over-arching conclusions we want, but at the end of the day, it looks drastically different from person to person. Is emotional eating a thing? Yes and no. The bigger question we need to be asking is: does it interfere with some people's health and well being? And if that answer is yes, which it quite certainly is, what are we going to do about it?
Frayn, M., & Knauper, B. (2016). Emotional eating and weight: A review. Current Psychology, advanced online publication, doi:10.1007/s12144-017-9577-9.
Koenders, P. G., & van Strien, T. (2011). Emotional eating, rather than lifestyle behavior, drives weight gain in a prospective study in 1562 employees. Journal of Occupational and Environmental Medicine, 53(11), 1287-1293.
Delahanty, L. M., Peyrot, M., & Shrader, P. J. (2013). Pre-treatment, psychological and behavioral predictors of weight outcomes among lifestyle intervention participants in the Diabetes Prevention Program (DPP). Diabetes Care, 36(1), 34-40.
Frayn, M., Ivanova, E., Carriere, K., Knäuper, B., & the McGill CHIP Healthy Weight Program Investigators. (2017, June). Emotional eating and weight loss in the McGill CHIP Healthy Weight Study. Poster presented at the International Society of Behavioral Nutrition and Physical Activity Annual Meeting, Victoria, British Columbia.
Werthmann, J., Renner, F., Roefs, A., Huibers, M. J. H., Plumanns, L., Krott, N., & Jansen, A. (2014). Looking at food in sad mood: Do attention biases lead emotional eaters into overeating after a negative MI? Eating Behaviors, 15, 230–236.
Adriaanse, M. A., Prinsen, S., de Witt Huberts, J. C., de Ridder, D. T., & Evers, C. (2016). 'I ate too much so I must have been sad': Emotions as a confabulated reason for overeating. Appetite, 103, 318-323.
Dohle, S., Hartmann, C., & Keller, C. (2014). Physical activity as a moderator of the association between emotional eating and BMI: Evidence from the Swiss Food Panel. Psychology & Health, 29, 1062-1080.
Tan, C. C., & Chow, C. M. (2014). Stress and emotional eating: The mediating role of eating dysregulation. Personality and Individual Differences, 66, 1-4.
Do we really overeat in response to positive emotions?


Premiere: 4/24/81. Karel Paukert, organ. 2nd Annual New Music Festival. Bowling Green State University.
Reviews: "Three of the most compelling works for instruments alone took their inspiration from cultures either historically or anthropologically remote from our own. Marilyn Shrude's Enuma Elish for mechanical action organ (1980), which received its first performance at the Festival, is a programmatic work based on the ancient poem of the same name. The poem relates the Babylonian myth of creation. The masses of sound exploring shifting densities and registration are reminiscent of parts of Ligeti's Volumina, but are used here in new ways and in a fresh context established by the work's program. The gradual build-up of sonority that opens the work, emerging out of silence, had an effect on me similar to that in the "creation" represented at the beginning of Das Rheingold. The unconventional performance techniques involved are fascinating in themselves and, for me, served to enhance the program: numerous small wooden wedges were used to hold down keys to create sustained sonorities. Two assistants to guest organist Karel Paukert were needed to insert and remove the wedges. These activities bore resemblance to what one could imagine as the rather cumbersome performance techniques used for ancient and early medieval organs with sliders. Through the information supplied in the program notes, the sonorities and unusual performance activities themselves evoked visions of antiquity, but I suspect that the full impact of the work will only be felt by comparing the score with the poem that inspired the music's creation. The score for this work should be especially interesting, and I hope it will soon be available." Lance Bruner. Perspectives of New Music. Fall-Winter 1980. Spring-Summer 1981.
"It is highly pictorial in a space-saga sort of way, and exploits the organ's resources most skillfully." Finn, Robert. The Cleveland Plain Dealer. 10/12/81.


text:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%% MooseBasedApp INTERFACE  %%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{MooseBasedApp Interface}
\subsubsection{Files}
In the \xmlNode{Files} section, as specified before, all of the files needed for
the code to run should be specified.
%
In the case of any MooseBasedApp, the files typically needed are the following:
\begin{itemize}
  \item MooseBasedApp GetPot input file
  \item Restart Files (if the calculation is instantiated from a restart point)
  \item Mesh Files (in case the mesh is externally specified)
  \item Any other generic input file (CSVs with Power histories, boundary conditions files, etc.)
\end{itemize}
Example:
\begin{lstlisting}[style=XML]
<Files>
  <Input name='mooseBasedApp.i' type=''>mooseBasedApp.i</Input>
  <Input name='0020_mesh.cpr' type=''>0020_mesh.cpr</Input>
  <Input name='0020.xdr.0000' type="">0020.xdr.0000</Input>
  <Input name='0020.rd-0' type="">0020.rd-0</Input>
  <Input name='exodus_mesh.e' type="">exodus_mesh.e</Input>
  <Input name='a_generic_additional_input_file.csv' type="Generic">a_generic_additional_input_file.csv</Input>
</Files>
\end{lstlisting}
If any file is tagged with the type \texttt{Generic}, it will be perturbed with the approach (wildcards)
 explained in the generic code interface (see  \ref{subsec:genericInterface}).

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{Models}
In the \xmlNode{Models} block particular MooseBasedApp executable needs to be specified.
%
Here is a standard example of what can be used to use with a typical MooseBasedApp (Bison) as the model:
\begin{lstlisting}[style=XML]
<Models>

      <executable>~path/to/Bison-opt</executable>

</Models>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{Distributions}
The \xmlNode{Distributions} block defines the distributions that are going
to be used for the sampling of the variables defined in the \xmlNode{Samplers}
block.
%
For all the possible distributions and all their possible inputs please see the
chapter about Distributions (see~\ref{sec:distributions}).
%
Here we give a general example of three different distributions:
\begin{lstlisting}[style=XML,morekeywords={name,debug}]
<Distributions>
    <Normal name='ThermalConductivity1'>
        <mean>1</mean>
        <sigma>0.001</sigma>
        <lowerBound>0.5</lowerBound>
        <upperBound>1.5</upperBound>
    </Normal>
    <Normal name='SpecificHeat'>
        <mean>1</mean>
        <sigma>0.4</sigma>
        <lowerBound>0.5</lowerBound>
        <upperBound>1.5</upperBound>
    </Normal>
    <Triangular name='ThermalConductivity2'>
        <apex>1</apex>
        <min>0.1</min>
        <max>4</max>
    </Triangular>
</Distributions>
\end{lstlisting}

It is good practice to name the distribution something similar to what kind of
variable is going to be sampled, since there might be many variables with the
same kind of distributions but different input parameters.
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{Samplers}
In the \xmlNode{Samplers} block we want to define the variables that are going
to be sampled.
%
\textbf{Example}:
We want to do the sampling of 3 variables:
\begin{itemize}
  \item Thermal Conductivity of the Fuel;
  \item Specific Heat Transfer Ratio of the Cladding;
  \item Thermal Conductivity of the Cladding.
\end{itemize}

We are going to sample these 3 variables using two different sampling methods:
Grid and Monte-Carlo.

In order to perturb any MooseBasedApp, the user needs to specify the variables to be
sampled indicating the path to the value separated with the symbol ``$|$''. For example,
if the variable that we want to perturb is specified in the input as follows:
\begin{lstlisting}[style=XML]
[Materials]
  ...
  [./heatStructure]
     ...
     thermal_conductivity = 1.0
     ...
  [../]
  ...
[]
\end{lstlisting}
the variable name in the Sampler input block needs to be named as follows:
\begin{lstlisting}[style=XML]
...
<Samplers>
  <aSampler name='aUserDefinedName' >
    <variable name='Materials|heatStructure|thermal_conductivity'>
      ...
    </variable>
  </aSampler>
</Samplers>
...
\end{lstlisting}

%
In case the variables have multiple entries, for example, variable `w' as shown in the following:
\begin{lstlisting}[style=XML]
[Functions]
  ...
  [./the_linear_combo]
    type = LinearCombinationFunction
    functions = 'xtimes twoxplus1 xsquared tover2'
    w = '3 -1.2 0.4 3'
  [../]
  ...
[]
\end{lstlisting}
The users can append `:' to the end of the variable, and use an integer number to indicate which
entry value to be perturbed by RAVEN.
For example, if the user wants to perturb the first
and third values of `w' in the aboved example, the RAVEN Sampler will be updated as follows:
\begin{lstlisting}[style=XML]
...
<Samplers>
  <aSampler name='aUserDefinedName' >
    <variable name='Functions|the_linear_combo|w:1'>
      ...
    </variable>
    <variable name='Functions|the_linear_combo|w:3'>
      ...
    </variable>
  </aSampler>
</Samplers>
...
\end{lstlisting}

%
In case some variables in external (\texttt{Generic} input files) need to be perturbed,
the wildcard approach can be used (for those variables):
\begin{lstlisting}[style=XML]
...
<Samplers>
  <aSampler name='aUserDefinedName' >
    <variable name='aWildCard1'>
      ...
    </variable>
        <variable name='aWildCard2'>
      ...
    </variable>
    <variable name='Materials|heatStructure|thermal_conductivity'>
      ...
    </variable>
  </aSampler>
</Samplers>
...
\end{lstlisting}
In this case the tagged file (\texttt{Generic}) will be parsed to find the variables
\texttt{\$RAVEN-aWildCard1\$} and \texttt{\$RAVEN-aWildCard1\$} and to replace their values
with the corresponding sampled variables (for more details, see  \ref{subsec:genericInterface})

In this example, we proceed to do so for both the Grid sampling and the Monte-Carlo sampling.
\begin{lstlisting}[style=XML,morekeywords={name,type,construction,lowerBound,steps,limit,initialSeed}]
<Samplers verbosity='debug'>
    <Grid name='myGrid'>
      <variable name='Materials|heatStructure1|thermal_conductivity' >
        <distribution>ThermalConductivity1</distribution>
        <grid         type='value' construction='custom' >0.6 0.7 0.8</grid>
      </variable>
      <variable name='Materials|heatStructure1|specific_heat' >
        <distribution >SpecificHeat</distribution>
        <grid         type='CDF'    construction='custom'>0.5 1.0 0.0</grid>
      </variable>
      <variable name='Materials|heatStructure2|thermal_conductivity'>
        <distribution  >ThermalConductivity2</distribution>
        <grid type='value' upperBound='4' construction='equal' steps='1'>0.5</grid>
      </variable>
      <variable name='aWildCard1'>
        <distribution  >ThermalConductivity2</distribution>
        <grid type='value' upperBound='4' construction='equal' steps='1'>0.5</grid>
      </variable>
    </Grid>
  <MonteCarlo name='MC_Sampler' limit='1000'>
      <variable name='Materials|heatStructure1|thermal_conductivity' >
        <distribution>ThermalConductivity1</distribution>
      </variable>
      <variable name='Materials|heatStructure1|specific_heat' >
        <distribution >SpecificHeat</distribution>
      </variable>
      <variable name='Materials|heatStructure2|thermal_conductivity'>
        <distribution  >ThermalConductivity2</distribution>
      </variable>
      <variable name='aWildCard1'>
        <distribution  >ThermalConductivity2</distribution>
      </variable>
  </MonteCarlo>
</Samplers>
\end{lstlisting}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{Steps}
For a MooseBasedApp, the \xmlNode{MultiRun} step type will most likely be
used, as first step.
%
First, the step needs to be named: this name will be one of the names used in
the \xmlNode{Sequence} block.
%
In our example, \texttt{Grid\_Sampler} and \texttt{MC\_Sampler}.
%
\begin{lstlisting}[style=XML,morekeywords={name,debug,re-seeding}]
     <MultiRun name='Grid_Sampler' >
\end{lstlisting}

With this step, we need to import all the files needed for the simulation:
\begin{itemize}
  \item MooseBasedApp YAML input file;
  \item eventual restart files (optional);
  \item other auxiliary files (e.g., powerHistory tables, etc.).
\end{itemize}
\begin{lstlisting}[style=XML,morekeywords={name,class,type}]
    <Input   class='Files' type=''>mooseBasedApp.i</Input>
    <Input   class='Files' type=''>0020_mesh.cpr</Input>
    <Input   class='Files' type=''>0020.xdr.0000</Input>
    <Input   class='Files' type=''>0020.rd-0</Input>
\end{lstlisting}
We then need to define which model will be used:
\begin{lstlisting}[style=XML]
    <Model  class='Models' type='Code'>MyMooseBasedApp</Model>
\end{lstlisting}
We then need to specify which Sampler is used, and this can be done as follows:
\begin{lstlisting}[style=XML]
    <Sampler class='Samplers' type='Grid'>Grid_Sampler</Sampler>
\end{lstlisting}
And lastly, we need to specify what kind of output the user wants.
%
For example the user might want to make a database (in RAVEN the database
created is an HDF5 file) and a DataObject of type PointSet, to use in sub-sequential
post-processing.
%
Here is a classical example:
\begin{lstlisting}[style=XML,morekeywords={class,type}]
    <Output  class='Databases' type='HDF5'>MC_out</Output>
    <Output  class='DataObjects' type='PointSet'>MCOutData</Output>
\end{lstlisting}

Following is the example of two MultiRun steps which use different sampling
methods (grid and Monte Carlo), and creating two different databases for each
one:
\begin{lstlisting}[style=XML]
<Steps verbosity='debug'>
  <MultiRun name='Grid_Sampler' verbosity='debug'>
    <Input  class='Files' type=''>mooseBasedApp.i</Input>
    <Input  class='Files' type=''>0020_mesh.cpr</Input>
    <Input  class='Files' type='' >0020.xdr.0000</Input>
    <Input  class='Files' type=''>0020.rd-0</Input>
    <Model  class='Models'    type='Code'>MyMooseBasedApp</Model>
    <Sampler class='Samplers'  type='Grid'>Grid_Sampler</Sampler>
    <Output  class='Databases' type='HDF5'>Grid_out</Output>
    <Output  class='DataObjects' type='PointSet'>gridOutData</Output>
  </MultiRun>
  <MultiRun name='MC_Sampler' verbosity='debug' re-seeding='210491'>
    <Input  class='Files' type=''>mooseBasedApp.i</Input>
    <Input  class='Files' type=''>0020_mesh.cpr</Input>
    <Input  class='Files' type='' >0020.xdr.0000</Input>
    <Input  class='Files' type=''>0020.rd-0</Input>
    <Model  class='Models'    type='Code'>MyMooseBasedApp</Model>
    <Sampler class='Samplers'  type='MonteCarlo' >MC_Sampler</Sampler>
    <Output  class='Databases' type='HDF5' >MC_out</Output>
    <Output  class='DataObjects' type='PointSet'>MCOutData</Output>
  </MultiRun>
</Steps>
\end{lstlisting}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{Databases}
As shown in the \xmlNode{Steps} block, the code is creating two database objects
called \texttt{Grid\_out} and \texttt{MC\_out}.
%
So the user needs to input the following:
\begin{lstlisting}[style=XML]
<Databases>
  <HDF5 name="Grid_out" readMode="overwrite"/>
  <HDF5 name="MC_out" readMode="overwrite"/>
</Databases>
\end{lstlisting}
As listed before, this will create two databases.
%
The files will have names corresponding to their \xmlAttr{name} appended with
the .h5 extension (i.e. \texttt{Grid\_out.h5} and \texttt{MC\_out.h5}).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{DataObjects}
As shown in the \xmlNode{Steps} block, the code is creating two DataObjects of type PointSet
called \texttt{gridOutData} and \texttt{MCOutData}.
%
So the user needs to input the following:
\begin{lstlisting}[style=XML]
<DataObjects>
    <PointSet name='gridOutData'>
      <Input>
          Materials|heatStructure2|thermal_conductivity,
          Materials|heatStructure1|specific_heat,
          Materials|heatStructure2|thermal_conductivity
      </Input>
      <Output>aveTempLeft</Output>
    </PointSet>
    <PointSet name='MCOutData'>
      <Input>
          Materials|heatStructure2|thermal_conductivity,
          Materials|heatStructure1|specific_heat,
          Materials|heatStructure2|thermal_conductivity
      </Input>
      <Output>aveTempLeft</Output>
    </PointSet>
</DataObjects>
\end{lstlisting}
As listed before, this will create two DataObjects that can be used in sub-sequential post-processing.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsubsection{OutStreams}
As fully explained in section~\ref{sec:outstream}, if the user want to print out or plot the content of a \textbf{DataObjects},
he needs to create an \textbf{OutStream} in the \xmlNode{OutStreams} XML block.
\\As it shown in the example below, for MooseBasedApp (and any other Code interface that might use the symbol $|$
for the Sampler's variable syntax), in the Plot \xmlNode{x} and \xmlNode{y} specification, the user needs to
utilize curly brackets.
\begin{lstlisting}[style=XML]
<OutStreams>
  <Print name='gridOutDataDumpCSV'>
    <type>csv</type>
    <source>gridOutData</source>
  </Print>
   <Plot verbosity='debug' name='test'   overwrite='False'>
    <plotSettings>
       <plot>
        <type>line</type>
        <x>
          MCOutData|Input|{Materials|heatStructure2|thermal_conductivity}
        </x>
        <y>MCOutData|Output|aveTempLeft</y>
        <kwargs><color>blue</color></kwargs>
      </plot>
    </plotSettings>
    <actions><how>screen,png</how></actions>
  </Plot>
</OutStreams>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%% Moose VectorPostProcessor INTERFACE  %%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{MooseVPP Interface}

The Moose Vector Post Processor is used mainly in the solid mechanics analysis.
This interface loads the values of the vector ouput processor to a \xmlNode{DataObjects} object.

To use this interface the [DomainIntegral] needs to be present in the MooseBasedApp's
 input file and the subnode \xmlNode{fileargs} should be defined in the subnode \xmlNode{Code} in
 the \xmlNode{Models} block of the RAVEN input file. The \xmlNode{fileargs} is required to have attributes with
the below specified values:

\begin{itemize}
    \item \xmlAttr{type}, \xmlDesc{string, required field}, must be ``MooseVPP''
    \item \xmlAttr{arg}, \xmlDesc{string, required field}, the string value attached to the vector post processor action
         while creating the output files.
\end{itemize}

This interface is actually identical to the MooseBasedApp interface, however there is
 few constraints on defining the output values of the post processor.
The definition of these outputs in the \xmlNode{DataObjects} depends on the definition of
 the [DomainIntegral].

The location of the value outputted is defined as \textit{ID\#} and the value is as
\textit{value\#}. The ''\#'' defines
the number of the location. The example below contains 3 locations in the [DomainIntegral]
where the values are outputted.

%
Example:
\begin{lstlisting}[style=XML]
 ...
  <Models>

      <executable>%FRAMEWORK_DIR%/../../moose/
        modules/combined/modules-%METHOD%</executable>
      <fileargs type = "MooseVPP" arg = "_J_1_" />
      <alias variable = "poissonsRatio" >
        Materials|stiffStuff|poissons_ratio</alias>
      <alias variable = "youngModulus"  >
        Materials|stiffStuff|youngs_modulus</alias>

  </Models>
 ...
  <DataObjects>
    <PointSet name="collset">
      <Input>youngModulus,poissonsRatio</Input>
      <Output>ID1,ID2,ID3,value1,value2,value3</Output>
    </PointSet>
  </DataObjects>
 ...
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%% MESH GENERATION COUPLED INTERFACES %%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Mesh Generation Coupled Interfaces}
Some software requires a provided mesh that requires a separate code run to generate.
In these cases, we use sampled geometric
variables to generate a new mesh for each perturbation of the original problem, then run the input with
the remainder of the perturbed parameters and the perturbed mesh.  RAVEN currently provides two interfaces for
this type of calculation, listed below.

%%%%%%%%%% CUBIT MOOSE INTERFACE %%%%%%%%%%
\subsubsection{MooseBasedApp and Cubit Interface}
Many MOOSE-based applications use Cubit (\url{https://cubit.sandia.gov}) to generate Exodus II files as
geometry and meshing for calculations.  To use the developed interface, Cubit's
bin directory must be added to the user's PYTHONPATH.  Input parameters for Cubit can be listed in a journal
(\texttt{.jou}) file.  Parameter values
are typically hardcoded into the Cubit command syntax, but variables may be
predefined in a journal file through Aprepro syntax.  This is an example of a journal
file that generates a rectangle of given height and width, meshes it, defines its
volume and sidesets, lists its element type, and writes it as an Exodus file:

%Cubit (\url{https://cubit.sandia.gov}) is a toolkit developed at Sandia National
%Laboratory used to create two- and three-dimensional finite element meshes with
%various options for defining geometric properties as a part of the grid. It is
%capable of reading and writing a variety of standard mesh file types, including
%Genesis or Exodus II (*.e) files.  As MOOSE applications use Exodus II files for
%meshes and results, Cubit is commonly used to generate meshes for problems of
%interest.  Cubit commands are used to create the geometry, mesh the object, and
%identify volumes, sidesets, and nodesets for a mesh.  These commands may be
%placed in journal files (*.jou) to be used as input to Cubit.  Parameter values
%are typically hardcoded into the Cubit command syntax, but variables may be
%predefined in a journal file through Aprepro syntax.  An example of a journal
%file that generates a rectangle of given height and width, meshes it, defines its
%volume and sidesets, lists its element type, and writes it as an Exodus file is given:

\begin{lstlisting}
#{x = 3}
#{y = 3}
#{out_name = "'out_mesh.e'"}
create surface rectangle width {x} height {y} zplane
mesh surface 1
set duplicate block elements off
block 1 surface 1
Sideset 1 curve 3
Sideset 2 curve 4
Sideset 3 curve 1
Sideset 4 curve 2
Block all element type QUAD4
export genesis {out_name} overwrite
\end{lstlisting}

The first three lines are the Aprepro variable definitions that RAVEN requires to
insert sampled variables.  All variables that RAVEN samples
need to be defined as Aprepro variables in the journal
file.
%These are typically geometric parameters, though almost anything that Cubit
%quantifies in a command may be defined as a variable and sampled through RAVEN
%such as internal mesh refinement values.
One essential caveat to running
this interface is that an Aprepro variable MUST be defined with the name "out\_name".
In order to run this script without RAVEN inserting the correct syntax for the
output file name and properly generate the Exodus file for a mesh, the output file
name is REQUIRED to be in both single and double quotation marks with the file
extension appended to the end of the file base name (e.g. '"output\_file.e"').

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Files}
\xmlNode{Files} works the same as in other interfaces with name and type
attributes for each node entry.  The \xmlAttr{name} attribute is a user-chosen internal
name for the file contained in the node, and \xmlAttr{type} identifies which base-level
interface the file is used within.  \xmlNode{type} should only be specified for inputs
that RAVEN will perturb.  For Moose input files, \xmlNode{type} should be \xmlString{MooseInput} and for
Cubit journal files, the \xmlNode{type} should be \xmlString{CubitInput}.  The node should contain the
path to the file from the working directory.  The following is an example
of a typical \xmlNode{Files} block.

\begin{lstlisting}[style=XML]
<Files>
  <Input name='moose_test' type='MooseInput'>simple_diffusion.i</Input>
  <Input name='mesh_in'    type='CubitInput'>rectangle.jou</Input>
  <Input name='other_file' type=''          >some_file_moose_input_needs.ext</Input>
</Files>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Models}
The user provides paths to executables and aliases for sampled variables within the
\xmlNode{Models} block.  The \xmlNode{Code} block will contain attributes name and
subType.  Name identifies that particular \xmlNode{Code} model within RAVEN, and
subType specifies which code interface the model will use. The \xmlNode{executable}
block should contain the absolute or relative (with respect to the current working
directory) path to the MooseBasedApp that RAVEN will use to run generated input
files.  The absolute or relative path to the Cubit executable is specified within
\xmlNode{preexec}.  If the \xmlNode{preexec} block is not needed, the
MooseBasedApp interface is probably preferable to the Cubit-Moose interface.

Aliases are defined by specifying the variable attribute in an \xmlNode{alias} node with
the internal RAVEN variable name chosen with the node containing the model
variable name.  The Cubit-Moose interface uses the same syntax as the
MooseBasedApp to refer to model variables, with pipes separating terms starting
with the highest YAML block going down to the individual parameter that RAVEN
will change.  To specify variables that are going to be used in the Cubit
journal file, the syntax is "Cubit|aprepro\_var".  The Cubit-Moose interface
will look for the Cubit tag in all variables passed to it and upon finding it,
send it to the Cubit interface.  If the model variable does not begin with \xmlString{Cubit},
the variable MUST be specified in the MooseBasedApp input file.  While the model
variable names are not required to have aliases defined (the \xmlNode{alias}
blocks are optional), it is highly suggested to do so not only to ensure brevity
throughout the RAVEN input, but to easily identify where variables are being sent
in the interface.

An example \xmlNode{Models} block follows.

\begin{lstlisting}[style=XML]
<Models>

    <executable>%FRAMEWORK_DIR%/../../moose/modules/combined/...
      modules-%METHOD%</executable>
    <preexec>/hpc-common/apps/local/cubit/13.2/bin/cubit</preexec>
    <alias variable="length">Cubit@y</alias>
    <alias variable="bot_BC">BCs|bottom|value</alias>

</Models>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Distributions}
The \xmlNode{Distributions} block defines all distributions used to
sample variables in the current RAVEN run.

For all the possible distributions and their possible inputs please
refer to the Distributions chapter (see~\ref{sec:distributions}).
%
It is good practice to name the distribution something similar to what kind of
variable is going to be sampled, since there might be many variables with the
same kind of distributions but different input parameters.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Samplers}
The \xmlNode{Samplers} block defines the variables to be sampled.

After defining a sampling scheme, the variables to be sampled and
their distributions are identified in the \xmlNode{variable} blocks.
The name attribute in the \xmlNode{variable} block must either be the
full MooseBasedApp model variable name or the alias name specified in
\xmlNode{Models}.  If the sampled variable is a geometric property
that will be used to generate a mesh with Cubit, remember the syntax for
variables being passed to journal files (Cubit|aprepro\_var).

For listings of available samplers
refer to the Samplers chapter (see~\ref{sec:Samplers}).

See the following for an example of a grid based sampler for
length and the bottom boundary condition (both of which have aliases
defined in \xmlNode{Models}).

\begin{lstlisting}[style=XML]
<Samplers>
  <Grid name="Grid_sampling">
    <variable name="length" >
      <distribution>length_dist</distribution>
      <grid type="value" construction="custom">1.0 2.0</grid>
    </variable>
    <variable name="bot_BC">
      <distribution>bot_BC_dist</distribution>
      <grid type="value" construction="custom">3.0 6.0</grid>
    </variable>
  </Grid>
</Samplers>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Steps,OutStreams,DataObjects}
This interface's \xmlNode{Steps}, \xmlNode{OutStreams}, and
\xmlNode{DataObjects} blocks do not deviate significantly from
other interfaces' respective nodes.  Please refer to previous
entries for these blocks if needed.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{File Cleanup}
The Cubit-Moose interface automatically removes files that are commonly
unwanted after the RAVEN run reaches completion. Cubit has been described as
"talkative" due to additional journal files with execution information
being generated by the program after every completed journal file run.
The quantity of these files can quickly become unwieldy if the working
directory is not kept clean; thus these files are removed.  In addition, some users
may wish to remove Exodus files after the RAVEN run is complete as
the typical size of each file is quite large and it is assumed that any
output quantities of interest will be collected by appropriate PostProcessors
and the OutStreams.  Exodus files are not automatically removed,
but by using the \xmlNode{deleteOutExtension} node in \xmlNode{RunInfo}, one
may specify the Exodus extension to save a fair amount of storage space
after RAVEN completes a sequence. For example:

\begin{lstlisting}[style=XML]
<RunInfo>
  ...
  <deleteOutExtension>e</deleteOutExtension>
  ...
</RunInfo>
\end{lstlisting}

%%%%%%%%%% BISON MESH SCRIPT MOOSE INTERFACE %%%%%%%%%%
\subsubsection{MooseBasedApp and Bison Mesh Script Interface}
For BISON users, a Python mesh generation script is included in
the \%BISON\_DIR\%/tools/UO2/ directory.  This script generates
3D or 2D (RZ) meshes for nuclear fuel rods using Cubit with
templated commands.  The BISON Mesh Script (BMS) is capable of
generating rods with discrete fuel pellets of various size in
assorted configurations.  To use this interface, Cubit's bin
directory must be added to the user's PYTHONPATH.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Files}
Similar to the Cubit-Moose interface, the BisonAndMesh interface
requires users to specify all files required to run their input
so that these file may be copied into the respective sequence's
working directory.  The user will give each file an internal
RAVEN designation with the name attribute, and the MooseBasedApp
and BISON Mesh Script inputs must be assigned their respective types
in another attribute of the \xmlNode{Input} node.  An example follows.

\begin{lstlisting}[style=XML]
<Files>
  <Input name='bison_test' type='MooseInput'>simple_bison_test.i</Input>
  <Input name='mesh_in'    type='BisonMeshInput'>coarse_input.py</Input>
  <Input name='other_file' type=''>some_file_moose_input_needs.ext</Input>
</Files>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Models}
The user provides paths to executables and aliases for sampled variables within the
\xmlNode{Models} block.  The \xmlNode{Code} block will contain attributes \xmlAttr{name} and
\xmlAttr{subType}.  \xmlAttr{name} identifies that particular \xmlNode{Code} model within RAVEN, and
\xmlAttr{subType} specifies which code interface the model will use. The \xmlNode{executable}
block should contain the absolute or relative (with respect to the current working
directory) path to the MooseBasedApp that RAVEN will use to run generated input
files.  The absolute or relative path to the mesh script python file is specified within
\xmlNode{preexec}.  If the \xmlNode{preexec} block is not needed, use the
MooseBasedApp interface.

Aliases are defined by specifying the variable attribute in an \xmlNode{alias} node with
the internal RAVEN variable name chosen with the node containing the model
variable name.  The BisonAndMesh interface uses the same syntax as the
MooseBasedApp to refer to model variables, with pipes separating terms starting
with the highest YAML block going down to the individual parameter that RAVEN
will change.  To specify variables that are going to be used in the BISON Mesh Script
python input, the syntax is "Cubit|dict\_name|var\_name".  The interface
will look for the Cubit tag in all variables passed to it and upon finding the tag,
send it to the BISON Mesh Script interface.  If the model variable does not begin with Cubit,
the variable MUST be specified in the MooseBasedApp input file.  While the model
variable names are not required to have aliases defined (the \xmlNode{alias}
blocks are optional), it is highly suggested to do so not only to ensure brevity
throughout the RAVEN input, but to easily identify where variables are being sent
in the interface.

An example \xmlNode{Models} block follows.

\begin{lstlisting}[style=XML]
<Models>

    <executable>%FRAMEWORK_DIR%/../../bison/bison-%METHOD%</executable>
    <preexec>%FRAMEWORK_DIR%/../../bison/tools/UO2/mesh_script.py</preexec>
    <alias variable="pellet_radius" >Cubit@Pellet1|outer_radius</alias>
    <alias variable="clad_thickness">Cubit@clad|clad_thickness</alias>
    <alias variable="fuel_k"        >Materials|fuel_thermal|thermal_conductivity</alias>
    <alias variable="clad_k"        >Materials|clad_thermal|thermal_conductivity</alias>

</Models>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Distributions}
The \xmlNode{Distributions} block defines all distributions used to
sample variables in the current RAVEN run.

For all the possible distributions and their possible inputs please
refer to the Distributions chapter (see~\ref{sec:distributions}).
%
It is good practice to name the distribution something similar to what kind of
variable is going to be sampled, since there might be many variables with the
same kind of distributions but different input parameters.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Samplers}
The \xmlNode{Samplers} block defines the variables to be sampled.

After defining a sampling scheme, the variables to be sampled and
their distributions are identified in the \xmlNode{variable} blocks.
The name attribute in the \xmlNode{variable} block must either be the
full MooseBasedApp model variable name or the alias name specified in
\xmlNode{Models}.  If the sampled variable is a geometric property
that will be used to generate a mesh with Cubit, remember the syntax for
variables being passed to journal files (Cubit|aprepro\_var).

For listings of available samplers
refer to the Samplers chapter (see~\ref{sec:Samplers}).

See the following for an example of a grid based sampler for
length and the bottom boundary condition (both of which have aliases
defined in \xmlNode{Models}).

\begin{lstlisting}[style=XML]
<Samplers>
  <Grid name="Grid_sampling">
    <variable name="length" >
      <distribution>length_dist</distribution>
      <grid type="value" construction="custom">1.0 2.0</grid>
    </variable>
    <variable name="bot_BC">
      <distribution>bot_BC_dist</distribution>
      <grid type="value" construction="custom">3.0 6.0</grid>
    </variable>
  </Grid>
</Samplers>
\end{lstlisting}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{Steps,OutStreams,DataObjects}
This interface's \xmlNode{Steps}, \xmlNode{OutStreams}, and
\xmlNode{DataObjects} blocks do not deviate significantly from
other interfaces' respective nodes.  Please refer to previous
entries for these blocks if needed.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\paragraph{File Cleanup}
The BisonAndMesh interface automatically removes files that are commonly
unwanted after the RAVEN run reaches completion. Cubit has been described as
"talkative" due to additional journal files with execution information
being generated by the program after every completed journal file run.
The BISON Mesh Script creates a journal file to run with cubit after reading input parameters;
so Cubit will generate its "redundant" journal files, and .pyc files will
litter the working directory as artifacts of the python mesh script
reading from the .py input files.  The quantity of these files can quickly
become unwieldy if the working directory is not kept clean, thus these
files are removed.  Some users
may wish to remove Exodus files after the RAVEN run is complete as
the typical size of each file is quite large and it is assumed that any
output quantities of interest will be collected by appropriate postprocessors
and the OutStreams.  Exodus files are not automatically removed,
but by using the \xmlNode{deleteOutExtension} node in \xmlNode{RunInfo}, one
may specify the Exodus extension (*.e) to save a fair amount of storage space
after RAVEN completes a sequence. For example:

\begin{lstlisting}[style=XML]
<RunInfo>
  ...
  <deleteOutExtension>e</deleteOutExtension>
  ...
</RunInfo>
\end{lstlisting}


Your audio system's sound quality is only as good as its components, and the Vanco FR0503R gold plated banana plugs have your connections covered. These solderless plugs use a screw-type connection to accept speaker wire up to 14 gauge. Red and black color rings keep your wiring safe and organized, so wiring your system is a breeze.
Very good quality. I like the freedom of selecting whether the wires come out in-line or at right angles to the plug. I have used these before in both configurations as necessary.