Center for Air Toxic Metals® (CATM®) 2003-2007
EPA Grant Number: CR830929Subproject: this is subproject number R830929 , established and managed by the Center Director under a main grant
(EPA does not fund or establish subprojects; EPA awards and manages the overall grant for this center).
Center: Center for Air Toxic Metals® (CATM®)
Center Director: Groenewold, Gerald
Title: Center for Air Toxic Metals® (CATM®) 2003-2007
Investigators: Pavlish, John H. , Benson, Steven A. , Collings, Mike , Crocker, Charlene , Dunham, Grant , Galbreath, Kevin C. , Hamre, Lucinda , Hill-Brandt, Katie , Holmes, Michael J. , Laudal, Dennis L. , Mibeck, Blaise , Miller, Stanley J. , Musich, Mark , Olson, Ed , Ralston, Nicholas V.C. , Raymond, Laura , Sharma, Ramesh , Sondreal, Everett , Swanson, Mike , Thompson, Jeffrey S. , Zhuang, Ye , Zygarlicke, Christopher J.
Current Investigators: Pavlish, John H. , Benson, Steven A. , Crocker, Charlene , Galbreath, Kevin C. , Heebink, Loreal V. , Holmes, Michael J. , Laumb, Jason D. , Martin, Christopher L. , Mibeck, Blaise , Ralston, Nicholas V.C. , Schmidt, Darren D. , Zhuang, Ye
Institution: University of North Dakota - Main Campus
EPA Project Officer: Stelz, Bill
Project Period: May 1, 2003 through September 30, 2006 (Extended to September 30, 2007)
Project Amount: $3,098,736
RFA: Targeted Research Center (2003) Recipients Lists
Research Category: Targeted Research
Objective:
The Center for Air Toxic Metals ® (CATM ®) Program is focused on conducting research directed toward minimizing the impact of air toxic metals on the environment by administering a practically oriented multidisciplinary research, development, and training program on the formation, behavior, measurement, control, and minimization of potentially toxic metal emissions from energy conversion systems through partnerships developed with industry, government, and research organizations.
Objective/Hypothesis :
- develop key information on air toxic metals behavior, state, and fate for risk assessment/control/risk management;
- develop/test/validate sampling and analysis techniques;
- enhance use of existing control technologies;
- identify/develop new, more effective control technologies;
- demonstrate new and existing technologies;
- develop empirical and theoretical predictive techniques;
- optimize utilization options and safe disposal of by-products;
- educate students and raise public awareness;
- evaluate the health impacts/implications of air toxic metals; and
- develop, test, and commercialize technologies through partnerships with industry.
Specifically, the research projects funded under this award will:
- further develop a fundamental understanding of mercury transformations in coal combustion flue gas environments;
- develop methods to improve measurement of mercury and chlorine in combustion flue gases;
- develop mercury control technologies;
- model mercury interactions on activated carbons and evaluate other sorbents and additives;
- study mercury–selenium interactions in aquatic ecosystems;
- investigate mercury and carbon-based sorbent reaction mechanisms; and
- undertake the development of methods for halogen speciation measurements in combustion systems.
Approach:
The overall approach of the CATM Program is to conduct basic and applied scientific-based research that provides answers to critical questions related to air toxic metals, emissions from industrial sources, and development of control technologies that can be applied by industry to control emissions. Advanced and proven sampling and analytical methods are developed, tested, and used to further characterize air toxic emissions and to develop a better understanding of the fate and formation of air toxic metals throughout industrial processes.
Expected Results:
These activities, which both EPA and industry believe are extremely important, will continue to develop a better understanding of air toxic metals formation, transport, fate, measurement, control, modeling, and health effects and, on an ongoing basis, will expeditiously provide up-to-date information that will benefit industrial, government, academic, and public sectors.
Abstract for R827649Journal Articles: 39 Displayed | Download in RIS Format
| Other center views: | All 137 publications | 53 publications in selected types | All 39 journal articles |
|---|
| Type | Citation | ||
|---|---|---|---|
|
|
Benson SA. Air quality III: mercury, trace elements, and particulate matter--Preface. Fuel Processing Technology 2004;85(6-7):423-424. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2003) R827649 (Final) |
Exit |
|
|
Benson SA, Laumb JD, Crocker CR, Pavlish JH. SCR catalyst performance in flue gases derived from subbituminous and lignite coals. Fuel Processing Technology 2005;86(5):577-613. |
CR830929 (2005) |
Exit |
|
|
Benson SA, Pavlish JH, Holmes MJ, Crocker CR, Galbreath KC, Zhaung Y. Mercury control testing in a pulverized lignite-fired system. Fuel Processing Technology 2009;90(11):1378-1387. |
CR830929 (2006) |
Exit Exit |
|
|
Brown TD, Smith DN, Hargis Jr. RA, O’Dowd WJ. Mercury measurement and its control: what we know, have learned, and need to further investigate. Journal of the Air & Waste Management Association 1999;49(6):628-640. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) |
Exit Exit |
|
|
Dronen LC, Moore AE, Kozliak EI, Seames WS. An assessment of acid wash and bioleaching pre-treating options to remove mercury from coal. Fuel 2004;83(2):181-186. |
CR830929 (2004) R827649 (2003) R827649 (Final) |
not available |
|
|
Galbreath KC, Zygarlicke CJ. Mercury transformations in coal combustion flue gas. Fuel Processing Technology 2000;65-66:289-310. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit |
|
|
Galbreath KC, Toman DL, Zygarlicke CJ, Huggins FE, Huffman GP, Wong JL. Nickel speciation of residual oil fly ash and ambient particulate matter using X-ray absorption spectroscopy. Journal of the Air & Waste Management Association 2000;50(11):1876-1886. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit Exit |
|
|
Galbreath KC, Toman DL, Zygarlicke CJ, Pavlish JH. Trace element partitioning and transformations during combustion of bituminous and subbituminous U.S. coals in a 7-kW combustion system. Energy & Fuels 2000;14(6):1265-1279. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit |
|
|
Galbreath KC, Zygarlicke CJ, Olson ES, Pavlish JH, Toman DL. Evaluating mercury transformation mechanisms in a laboratory-scale combustion system. Science of the Total Environment 2000;261(1-3):149-155. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit |
|
|
Galbreath KC, Crocker CR, Nyberg CM, Huggins FE, Huffman GP, Larson KP. Nickel speciation measurements of urban particulate matter: method evaluation and relevance to risk assessment. Journal of Environmental Monitoring 2003;5(3):56N-61N. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2003) R827649 (Final) |
Exit |
|
|
Galbreath KC, Zygarlicke CJ. Formation and chemical speciation of arsenic-, chromium-, and nickel-bearing coal combustion PM2.5. Fuel Processing Technology 2004;85(6-7):701-726. |
CR830929 (2004) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit |
|
|
Galbreath KC, Zygarlicke CJ, Tibbetts JE, Schulz RL, Dunham GE. Effects of NOx, α-Fe2O3, γ-Fe2O3, and HCl on mercury transformations in a 7-kW coal combustion system. Fuel Processing Technology 2005;86(4):429-448. |
CR830929 (2004) CR830929 (2005) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit |
|
|
Galbreath KC, Schulz RL, Toman DL, Nyberg CM, Huggins FE, Huffman GP, Zillioux EJ. Nickel and sulfur speciation of residual oil fly ashes from two electric utility steam-generating units. Journal of the Air & Waste Management Association 2005;55(3):309-318. |
CR830929 (2005) |
|
|
|
Hassett DJ, Heebink LV, Pflughoeft-Hassett DF. Potential for mercury vapor release from coal combustion by-products. Fuel Processing Technology 2004;85(6-7):613-620. |
CR830929 (2004) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit |
|
|
Heebink LV, Hassett DJ. Release of mercury vapor from coal combustion ash. Journal of the Air & Waste Management Association 2002;52(8):927-930. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2002) R827649 (Final) |
Exit Exit |
|
|
Jensen RR, Karki S, Salehfar H. Artificial neural network-based estimation of mercury speciation in combustion flue gases. Fuel Processing Technology 2004;85(6-7):451-462. |
CR830929 (2004) R827649 (2003) R827649 (Final) |
Exit |
|
|
Gupta H, Benson SA, Fan L-S, Laumb JD, Olson ES, Crocker CR, Sharma RK, Knutson RZ, Rokanuzzaman ASM, Tibbetts JE. Pilot-scale studies of NOx reduction by activated high-sodium lignite chars: a demonstration of the CARBONOX process. Industrial and Engineering Chemistry Research 2004;43(18):5820-5827. |
CR830929 (2005) |
Exit |
|
|
Laudal DL, Pavlish JH, Graves J, Stockdill D. Mercury mass balances: a case study of two North Dakota power plants. Journal of the Air & Waste Management Association 2000;50(10):1798-1804. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit Exit |
|
|
Laudal DL, Thompson JS, Pavlish JH, Brickett LA, Chu P. Use of continuous mercury monitors at coal-fired utilities. Fuel Processing Technology 2004;85(6-7):501-511. |
CR830929 (2004) R827649 (2003) R827649 (Final) |
Exit |
|
|
Laudal DL, Thompson JS, Pavlish JH, Brickett L, Chu P, Srivastava RK, Lee CW, Kilgroe J. Mercury speciation at power plants using SCR and SNCR control technologies. EM Magazine 2003;(Feb):16-22. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2002) R827649 (2003) R827649 (Final) R827649C001 (Final) |
Exit |
|
|
Laumb JD, Benson SA, Olson EA. X-ray photoelectron spectroscopy analysis of mercury sorbent surface chemistry. Fuel Processing Technology 2004;85(6-7):577-585. |
CR830929 (2004) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit |
|
|
Olson ES, Sharma RK, Pavlish JH. On the analysis of mercuric nitrate in flue gas by GC-MS. Analytical and Bioanalytical Chemistry 2002;374(6):1045-1049. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2002) R827649 (Final) |
Exit |
|
|
Olson ES, Laumb JD, Benson SA, Dunham GE, Sharma RK, Mibeck BA, Miller SJ, Holmes MJ, Pavlish JH. Chemical mechanisms in mercury emission control technologies. Journal de Physique IV 2003;107:979-982. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2003) R827649 (Final) |
Exit Exit |
|
|
Olson ES, Crocker CR, Benson SA, Pavlish JH, Holmes MJ. Surface compositions of carbon sorbents exposed to simulated low-rank coal flue gases. Journal of the Air & Waste Management Association 2005;55(6):747-754. |
CR830929 (2004) CR830929 (2005) R827649 (2003) R827649 (Final) |
Exit Exit |
|
|
Pavlish JH, Sondreal EA, Mann MD, Olson ES, Galbreath KC, Laudal DL, Benson SA. Status review of mercury control options for coal-fired power plants. Fuel Processing Technology 2003;82(2-3):89-165. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit Exit |
|
|
Pavlish JH, Holmes MJ, Benson SA, Crocker CR, Galbreath KC. Application of sorbents for mercury control for utilities burning lignite coal. Fuel Processing Technology 2004;85(6-7):563-576. |
CR830929 (2004) R827649 (2003) R827649 (Final) |
Exit |
|
|
Pflughoeft-Hassett DF, Hassett DJ, Heebink LV, Buckley TD. The current state of the science related to the re-release of mercury from coal combustion products. Ash at Work 2006;1:26-27. |
CR830929 (2006) |
Exit |
|
|
Ralston NVC. Selenium health benefit values as seafood safety criteria. EcoHealth 2008;5(4):442-455. |
CR830929 (2006) |
Exit |
|
|
Raymond LJ, Ralston NVC. Mercury: selenium interactions and health implications. Seychelles Medical and Dental Journal 2004;7(1):72-77. |
CR830929 (2004) R827649 (Final) |
Exit |
|
|
Sondreal EA, Pavlish JH, Benson SA, Feeley T. Status of particulate matter research and development. Filtration & Separation 1999;36(2):11. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2000) R827649 (Final) |
Exit Exit |
|
|
Sondreal EA, Jones ML, Groenewold GH. Tides and trends in the world's electric power industry. The Electricity Journal 2001;14(1):61-79. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (Final) |
Exit |
|
|
Sondreal EA, Benson SA, Hurley JP, Mann MD, Pavlish JH, Swanson ML, Weber GF, Zygarlicke CJ. Review of advances in combustion technology and biomass cofiring. Fuel Processing Technology 2001;71(1-3):7-38. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (2001) R827649C001 (2001) R827649C001 (Final) |
Exit |
|
|
Sondreal EA, Benson SA, Pavlish JH, Ralston NVC. An overview of Air Quality III: Mercury, Trace Elements, and Particulate Matter. Fuel Processing Technology 2004;85(6-7):425-440. |
CR830929 (2004) R827649 (2003) R827649 (Final) |
Exit |
|
|
Xin M, Gustin MS, Ladwig K, Pflughoeft-Hassett DF. Air-substrate mercury exchange associated with landfill disposal of coal combustion products. Journal of the Air & Waste Management Association 2006;56(8):1167-1176. |
CR830929 (2006) |
Exit |
|
|
Zhao Y, Mann MD, Pavlish JH, Mibeck BAF, Dunham GE, Olson ES. Application of gold catalyst for mercury oxidation by chlorine. Environmental Science & Technology 2006;40(5):1603-1608. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) R827649 (Final) |
Exit |
|
|
Zhao Y, Mann MD, Olson ES, Pavlish JH, Dunham GE. Effects of sulfur dioxide and nitric oxide on mercury oxidation and reduction under homogeneous conditions. Journal of the Air & Waste Management Association 2006;56(5):628-635. |
CR830929 (2004) CR830929 (2005) CR830929 (2006) |
Exit Exit |
|
|
Zhuang Y, Zygarlicke CJ, Galbreath KC, Thompson JS, Holmes MJ, Pavlish JH. Kinetic transformation of mercury in coal combustion flue gas in a bench-scale entrained-flow reactor. Fuel Processing Technology 2004;85(6-7):463-472. |
CR830929 (2004) R827649 (2002) R827649 (2003) R827649 (Final) |
Exit |
|
|
Zhuang Y, Thompson JS, Zygarlicke CJ, Pavlish JH. Development of a mercury transformation model in coal combustion flue gas. Environmental Science & Technology 2004;38(21):5803-5808. |
CR830929 (2004) R827649 (Final) |
Exit |
|
|
Zhuang Y, Laumb J, Liggett R, Holmes M, Pavlish JH. Impacts of acid gases on mercury oxidation across SCR catalyst. Fuel Processing Technology 2007;88(10):929-934. |
CR830929 (2006) |
Exit Exit |
Supplemental Keywords:
Air, mercury, emissions, adsorption, absorption, chemical transport, health effects, human health, toxics, particulates, metals, sorbents, oxidants, nitrogen oxides, sulfates, pollution prevention, clean technologies, innovative technology, renewable, waste reduction, waste minimization, cost-benefit, environmental chemistry, physics, engineering, pathology, modeling, monitoring, analytical, measurement methods, industry, selenium, mercury sorbents, mercury additives., Scientific Discipline, Air, ENVIRONMENTAL MANAGEMENT, air toxics, Health Risk Assessment, Environmental Monitoring, Atmospheric Sciences, Risk Assessment, emission control strategies, air quality standards, control, aerosol particles, mercury emissions, air sampling, airborne metals, exposure assessmentProgress and Final Reports:
2004 Progress Report2005 Progress Report
2006 Progress Report


Structures
The following structures are available globally.
-
The
See moreContextRef
type acts as a lightweight Swift reference to an underlyingcairo_t
instance. It exposes methods that can operate on this data type throughContextProtocol
conformance. UseContextRef
only as anunowned
reference to an existingcairo_t
instance.Declaration
Swift
public struct ContextRef : ContextProtocol
-
The
See moreDeviceRef
type acts as a lightweight Swift reference to an underlyingcairo_device_t
instance. It exposes methods that can operate on this data type throughDeviceProtocol
conformance. UseDeviceRef
only as anunowned
reference to an existingcairo_device_t
instance.Declaration
Swift
public struct DeviceRef : DeviceProtocol
-
The
See moreSurfaceRef
type acts as a lightweight Swift reference to an underlyingcairo_surface_t
instance. It exposes methods that can operate on this data type throughSurfaceProtocol
conformance. UseSurfaceRef
only as anunowned
reference to an existingcairo_surface_t
instance.Declaration
Swift
public struct SurfaceRef : SurfaceProtocol
-
The
See moreMatrixRef
type acts as a lightweight Swift reference to an underlyingcairo_matrix_t
instance. It exposes methods that can operate on this data type throughMatrixProtocol
conformance. UseMatrixRef
only as anunowned
reference to an existingcairo_matrix_t
instance.Declaration
Swift
public struct MatrixRef : MatrixProtocol
-
The
See morePatternRef
type acts as a lightweight Swift reference to an underlyingcairo_pattern_t
instance. It exposes methods that can operate on this data type throughPatternProtocol
conformance. UsePatternRef
only as anunowned
reference to an existingcairo_pattern_t
instance.Declaration
Swift
public struct PatternRef : PatternProtocol
-
The
See moreRegionRef
type acts as a lightweight Swift reference to an underlyingcairo_region_t
instance. It exposes methods that can operate on this data type throughRegionProtocol
conformance. UseRegionRef
only as anunowned
reference to an existingcairo_region_t
instance.Declaration
Swift
public struct RegionRef : RegionProtocol
-
The
See moreFontOptionsRef
type acts as a lightweight Swift reference to an underlyingcairo_font_options_t
instance. It exposes methods that can operate on this data type throughFontOptionsProtocol
conformance. UseFontOptionsRef
only as anunowned
reference to an existingcairo_font_options_t
instance.Declaration
Swift
public struct FontOptionsRef : FontOptionsProtocol
-
The
See moreFontFaceRef
type acts as a lightweight Swift reference to an underlyingcairo_font_face_t
instance. It exposes methods that can operate on this data type throughFontFaceProtocol
conformance. UseFontFaceRef
only as anunowned
reference to an existingcairo_font_face_t
instance.Declaration
Swift
public struct FontFaceRef : FontFaceProtocol
-
The
See moreScaledFontRef
type acts as a lightweight Swift reference to an underlyingcairo_scaled_font_t
instance. It exposes methods that can operate on this data type throughScaledFontProtocol
conformance. UseScaledFontRef
only as anunowned
reference to an existingcairo_scaled_font_t
instance.Declaration
Swift
public struct ScaledFontRef : ScaledFontProtocol
-
The
See morePathRef
type acts as a lightweight Swift reference to an underlyingcairo_path_t
instance. It exposes methods that can operate on this data type throughPathProtocol
conformance. UsePathRef
only as anunowned
reference to an existingcairo_path_t
instance.Declaration
Swift
public struct PathRef : PathProtocol
-
The
See moreRectangleRef
type acts as a lightweight Swift reference to an underlyingcairo_rectangle_t
instance. It exposes methods that can operate on this data type throughRectangleProtocol
conformance. UseRectangleRef
only as anunowned
reference to an existingcairo_rectangle_t
instance.Declaration
Swift
public struct RectangleRef : RectangleProtocol
-
The
See moreRectangleIntRef
type acts as a lightweight Swift reference to an underlyingcairo_rectangle_int_t
instance. It exposes methods that can operate on this data type throughRectangleIntProtocol
conformance. UseRectangleIntRef
only as anunowned
reference to an existingcairo_rectangle_int_t
instance.Declaration
Swift
public struct RectangleIntRef : RectangleIntProtocol
-
Undocumented
See moreDeclaration
Swift
public struct cairo


14 January 2020
My name is Gunther Rotsch. I was born in 1965 in Germany and live now in Mellingen, a small village close-by Zurich in Switzerland.
I studied Information Science at the University of Applied Science in Mannheim, Germany. After finishing my study, I worked for a consulting company for two years. After that I worked for 10 years as a freelancer in software development projects. Then I was employed by consulting companies and software application companies. Up until 2000 I mainly developed with C ++ on Unix systems. After that my focus changed to Java Enterprise Systems.
I have been developing business applications as a lead developer or architect for 20+ years. Although my focus is on Java / Jarkata EE (full stack), I am open to other technologies such as Web, JavaScript, Python or Go.
In addition to architecture work and SOLID software design, I like to work "hands-on" in programming. I am very familiar with modern approaches such as clean coding, test-driven development and agile methods. The quality of the developed products and application of modern development processes are particularly close to my heart. This includes Static Code analysis (SonarQube), test automation, continuous integration and continuous deployment.
In the past four years, I have intensified with microservices / self-contained services, cloud-native applications (Design for Scalability, Resilience, Reliability, Monitoring), REST API Design (OpenAPI / Swagger).
I have practical experience in the deployment of containerized applications with Docker, Kubernetes and OpenShift as well as in setting up the necessary automated deployment processes. Most recently, I also have made experience with Ergon’s Web Application Firewall and roll-outs with Ansible, which complements my DevOps skills.


Preparation time
over 2 hours
Cooking time
30 mins to 1 hour
Serves
Serves 8-10
Dietary
Three really is the magic number when it comes to ice cream and when it's finished with a prettily tinted meringue who can resist?
Equipment and preparation: for this recipe you will need a 3 litre/5¼pint pudding bowl, a sugar thermometer, a piping bag fitted with a 2D star nozzle and a freestanding mixer with a whisk attachment.
Line a 3 litre/5¼pint pudding bowl with cling film. In a large bowl or a freestanding mixer, beat the vanilla ice cream to soften a little then spoon into the base of the pudding bowl. Level with a spatula and freeze for one hour, or until firm.
Wipe out the mixing bowl and add the strawberry ice cream. Beat to soften a little then spoon over the vanilla ice cream. Level with a spatula and freeze for one hour, or until firm.
Preheat the oven to 190C(170C fan)/375F/Gas 5. Lightly grease a 20cm/8in sandwich tin and line the base with baking parchment.
For the sponge base, place the eggs and sugar into a large bowl and beat at full speed with an electric whisk until the mixture is pale in colour and thick enough to just leave a trail when the whisk is lifted.
Sift the flour and cocoa powder over the surface of the mixture and gently fold in with a metal spoon or spatula. Pour the melted butter down the side of the bowl and gently fold in.
Pour into the prepared tin and tilt the tin to allow the mixture to spread evenly to the sides. Bake for about 10–12 minutes, or until springy to the touch and beginning to shrink from the sides of the tin. Turn out and leave to cool on a wire rack.
For the filling, in a large bowl or mixer, beat the chocolate ice cream to soften a little then spread over the strawberry ice cream. Level with a spatula and freeze for one hour, or until firm.
Place the cold sponge on an ovenproof serving dish. Turn the ice cream out onto the sponge and pop it back in the freezer while you are making the meringue.
Preheat the oven to 240C(220C fan)/460F/Gas 8½.
To make the meringue, place the sugar and six tablespoons of water in a heavy-based saucepan. Stir the sugar and water over a medium heat until the sugar dissolves, then bring to a fast boil until it reaches 110C/230F.
Whisk the egg whites in a large bowl of an electric mixer until stiff peaks form when the whisk is removed.
When the syrup temperature reaches 115C/240F on a sugar thermometer, slowly and carefully pour the syrup over the egg whites in a thin stream while continuing to whisk. Taking care not to let the syrup run onto the beaters as it may splash.
Continue whisking for about 15 minutes, or until the meringue is completely cold.
Take the cake and ice cream from the freezer and remove the cling film. Using a palette knife, spread a thin layer of meringue all over the ice cream and sponge to form a coating.
Fit a large disposable piping bag with a 2D star nozzle. Using a paint brush or small pastry brush, paint a line of pink gel paste up the inside of the bag in a line from the nozzle to the top. Repeat on the opposite side with the yellow gel paste. Spoon the meringue into the piping bag.
Starting from the top of the dome of ice cream and working quickly, pipe small rosettes of meringue over the dome of ice cream, until completely covered.
Bake in the preheated oven for about 4-5 minutes, or until golden-brown. Decorate with mixed berries and serve immediately.


LOCAL PLATFORM
Quant Research
On-Premise
Securely deploy quantitative
strategies on-premise with
proprietary datasets.


public class StaticContentDownloader
extends java.lang.Object
StaticContentDownloader
aids in managing the parallel download of resources. The goal is to better
simulate the download behavior of real browsers. The number of threads working in parallel is controlled by
configuration. Note that there is no differentiation between requests to different domains.| Constructor and Description |
|---|
StaticContentDownloader(com.xceptance.xlt.engine.XltWebClient webClient,
int threadCount,
boolean userAgentUID)
Creates a new RequestQueue object and initializes it with the given web client and the number of threads which
process the requests.
|
| Modifier and Type | Method and Description |
|---|---|
void |
addRequest(java.net.URL url)
Adds the given URL to the list of URLs to be loaded.
|
boolean |
isParallelModeEnabled()
Indicates whether or not the parallel execution of requests is enabled.
|
void |
setParallelModeEnabled(boolean value)
Enables or disables the parallel execution of requests.
|
void |
shutdown()
Shuts this request queue down.
|
void |
waitForCompletion()
Waits until all previously added requests have been executed.
|
public StaticContentDownloader(com.xceptance.xlt.engine.XltWebClient webClient, int threadCount, boolean userAgentUID)
webClient
- the web client to usethreadCount
- the number of threadsuserAgentUID
- do we need dynamic user agent identifierspublic void addRequest(java.net.URL url)
url
- the URL to loadpublic boolean isParallelModeEnabled()
public void setParallelModeEnabled(boolean value)
value
- the new statepublic void shutdown()
public void waitForCompletion()


Status
Published
Fair
CoopLag 2020
Date Created
20/09/2020 23:00 AM
Package
Standard
Template
Outdoor#20
Vendor's Category
New Category
Basic
$1000
Edit Faetures
Edit
Create Speakers
Stepup Vendor's Sign Up
Booth Settings
Advert Settings
Raffle
Events
Vendor's Signup link
New Link
Link
Form Template
www.cooplag.com
Form 1
Form Template
New Form
Form Name
Field title
Option 1
Option 2
Option 3
Option 4
Add Another Field


| Interface | Description |
|---|---|
| MPView<M> |
Created by carrotji on 2017-02-25.
|
| Class | Description |
|---|---|
| AddMoodActivity |
This is the main activity to add a mood.
|
| AddMoodActivityTest |
Created by Carlo on 2017-03-12.
|
| BuildConfig | |
| DeleteMoodActivityTest |
Created by carrotji on 2017-03-13.
|
| EditMapActivity |
EditMapActivity is for user to pick a location, place a marker
on a Map and pass LatLng to EditMoodActivity.
|
| EditMoodActivity |
This is the main activity to edit a mood.
|
| EditMoodActivityTest |
Created by carrotji on 2017-03-13.
|
| ElasticsearchMPController |
This is the main Elastic search controller.
|
| ElasticsearchMPController.AddUsersTask |
This task adds a participant to the elastic search server.
|
| ElasticsearchMPController.GetOneUserTask |
This task gets one single participant from the elastic search server
|
| ElasticsearchMPController.GetUsersTask |
This task gets all of the participants from the elastic search server
|
| ElasticsearchMPController.UpdateUsersTask |
This is the main task used to update a user in the elastic search server.
|
| ExampleUnitTest |
Example local unit test, which will execute on the development machine (host).
|
| FilterActivityTest |
ALL TESTS MUST BE RUN ON AN NEXUS 5 WITH AN API OF 22.
|
| FilteredDateActivity |
This activity is used to view participant mood events filtered by the most recent seven days.
|
| FilteredLocationActivity |
This activity is used to view participant mood events filtered by location.
|
| FilteredMoodActivity |
This activity is used to view participant mood events filtered by emotional states.
|
| FilteredTextActivity |
This activity is used to view participant mood events filtered by text or key word.
|
| FilterFollowDateActivity |
This activity is used to view all of the moods of people that the participant
follows.
|
| FilterFollowLocationActivity |
This activity is used to view all of the moods of people that the participant
follows.
|
| FilterFollowMoodActivity |
This activity shows only one type of mood that was specified from the option in the main
activity.
|
| FilterFollowTextActivity |
This activity is used to view all of the moods of people that the participant
follows.
|
| FollowActivity |
This activity is used when a participant wants to follow another participant.
|
| FollowAdapter |
The FollowAdapter class created a listView for FollowActivity,
this listView contains follow button.
|
| FollowerRequestActivity |
This activity is used to view the follower requests
From clicking the menu in the Navigation drawer.
|
| FollowerRequestActivityTest |
* ALL TESTS MUST BE RUN ON AN NEXUS 5 WITH AN API OF 22.
|
| FollowerRequestAdapter |
The FollowerRequestAdapter class created a listView for FollowerRequestActivity,
this listView contains acceptButton and declineButton.
|
| FollowingActivityTest |
Created by Carlo on 2017-04-03.
|
| FollowingListActivity |
This class is used to view all the participants someone follows.
|
| FollowingListAdapter |
The FollowingListAdapter class created a listView for FollowingListActivity,
this listView contains unfollow button.
|
| FollowingViewActivity |
Fragment for mood events of the people you are following
This fragment will only show the most recent mood from the participants you are following,
provided that they have a mood.
|
| GPSTracker |
This is GPSTracker class, used for getting the current location
of the device.
|
| GraphActivity |
This is the bar chart activity class of the statistics.
|
| MainMPController |
Main controller used in the App.
|
| Manifest | |
| Manifest.permission | |
| MapActivity |
The Map activity is used for viewing the participant current location,
view mood events that have location and view other participant mood event
with location that is 5 km near me.
|
| MarkerActivity |
The Marker Activity is for viewing map of mood events,
it is used when filtering mood events of the user or
the following participants by location.
|
| Mood |
This is the Mood class that instantiates a new Mood.
|
| MoodFollowerListAdapter |
This is for creating mood follower list, displaying emotional states,
Date, and trigger to the all the FilterActivity.
|
| MoodIcon |
This class is used for getting the correct png icon and the correct color associated\n
with the selected mood.
|
| MoodIconAdapter |
This is for creating mood icons into a gridview
Taken from https://developer.android.com/guide/topics/ui/layout/gridview.html
Created by carrotji on 2017-03-06.
|
| MoodListAdapter |
This is for creating mood list, displaying emotional states,
Date, and trigger to the MoodListViewActivity.
|
| MoodListViewActivity |
Main Fragment for the user mood events activity
Created by carrotji on 2017-03-25.
|
| MoodPlus | |
| MoodPlusActivity |
This is the main activity class of the MoodPlus application.
|
| MoodPlusApplication | |
| MoodTest |
Created by Carlo on 2017-04-02.
|
| MPModel<V extends MPView> |
Created by carrotji on 2017-02-25.
|
| OfflineDataController |
This class is used as a controller that handles offline behavior.
|
| Participant |
This is the main participant class which contains a Jest Id for elastic search,
a moodlist that contains their own list of moods, a following moodlist, and 2 lists for
who they follow and who is following them.
|
| ParticipantTest |
Created by Carlo on 2017-02-26.
|
| R | |
| R.anim | |
| R.animator | |
| R.attr | |
| R.bool | |
| R.color | |
| R.dimen | |
| R.drawable | |
| R.id | |
| R.integer | |
| R.layout | |
| R.menu | |
| R.mipmap | |
| R.string | |
| R.style | |
| R.styleable | |
| R.xml | |
| SaveOffline |
Class that stores and manages offline data.
|
| StatsActivity |
This is the pie chart activity class of the statistics.
|
| User |
This is a general abstract user class.
|
| UserMoodList |
This is the main class that defines the mood list of a user.
|
| UserMoodListTest |
Created by Carlo on 2017-02-25.
|
| ViewMoodActivity |
This is for viewing mood events.
|
| ViewNewMoodActivityTest |
Created by Carlo on 2017-03-13.
|
| WelcomeActivity |
This is the start up activity, allow the user to log in to
the MoodPlus Application.
|
| WelcomeActivityTest |
Created by carrotji on 2017-03-13.
|


Feature improvements
- Allow "eap" to be listed in Post-Auth-Type Reject
so that it sends EAP-Fail and Message-Authenticator.
Bug Fixes
- Fix typo in code checking for blocked threads.
Closes #880.
- Added more $(EXEEXT) to module utilities so that it
builds on Cygwin. Closes #875.
- Note that we don't need to generate ephemeral RSA keys.
- Port detail file fixes from v3.
- Use correct destination port for replies to DHCP relay.
- rlm_perl can store multiple tagged attributes of the
same name.
- Update EAP-TLS methods for TLSv1.2
- Fix load-balance sections. Closes #945


--- layout: tool title: "String Tools" author: max permalink: /tools/string-tools excerpt: "String manipulation tool" date: 2016-11-04 18:57:00 +1100 categories: - tools tags: - string-tools - --- Sometimes you just need to play with some strings.
Various online String and Number tools. Convert numbers between generic bases. Encode and format strings.


Introduction to Packages
A software package is a collection of files that make up a program. These
files may all be combined into one package file for distribution or
downloading, to be extracted and placed in their correct locations when
the package is installed.
A package management system automates most of the work in installing and
deleting programs. Because packages are usually pre-compiled, you do not
have to worry about Makefiles and configure scripts when
installing. Because the package management system keeps track of all
packages, it can remove all trace of a program when uninstalling.
Installed Packages
Packages are organised into classes and subclasses, like System
or X11/Utilities. At the top of the main page is a tree of folders
and packages, in which each folder represents a class. To open a folder, simply
click on it. To view more information about a package, click on its name.
Below the package tree is a form for searching the package database. This
will search for packages whose name or description matches whatever text
you enter.
Install a New Package
Below the package search button is a form for installing a new package.
You may install either from a file on your system, a file on the computer
on which you are running your web browser, or from an FTP or HTTP URL.
In the last case, Webmin will contact the FTP server or web site and download
the package file. If your system is behind a firewall, make sure you have
the proxy servers configured correctly in the Webmin Configuration
module.
Identify a File
At the bottom of the main page is a form for identifying some file on
your system. You may enter either an absolute path like
/etc/inetd.conf, or a command like elm. Webmin will attempt
to find the file in the package management system, and display information
about the file and the packages that use it.


for s=1:numel(subjects)
subj = subjects{s};
inpath = [indir subj '/'];
outpath = [outdir subj '/'];
load([outpath 'batch1_summary.mat']);
if ~strcmp(subj, cnt_stats.subj)
disp(['subj inconsistent ' subj]);
continue;
end
cd(inpath);
tmp = dir('*.cnt');
cnts = {tmp.name};
cd(this_dir);
all_eeg = [];
for c=1:numel(cnts)
eeg = epoch_data([inpath cnts{c}],relevant_events,correct_responses,stims,epoch_limits,baseline);
if isfield(eeg.event,'duration')
eeg.event = rmfield(eeg.event, 'duration');
end
eeg = eeg_checkset(eeg);
all_eeg = [all_eeg eeg];
clear eeg;
end
if numel(all_eeg)>1
eeg = pop_mergeset(all_eeg,1:numel(all_eeg),0);
eeg = eeg_checkset(eeg);
else
eeg = all_eeg;
end
clear all_eeg;
mix_matrix = cnt_stats.mix_matrix;
rejcomps = find(max(cnt_stats.similarity,[],1)> corr_threshold);
winv = pinv(mix_matrix);
keepcomps = setdiff([1:size(mix_matrix,1)],rejcomps);
icaact = mix_matrix(keepcomps,:) * reshape(eeg.data,eeg.nbchan,[]);
num_keepcomps = size(icaact,1);
icaact = reshape(icaact,num_keepcomps,eeg.pnts,[]);
ica_trial_gfp = squeeze(sum(abs(icaact),2));
gfp_30p = prctile(ica_trial_gfp',30);
clear stdev;
for comp =1:num_keepcomps
good_trials = find(squeeze(ica_trial_gfp(comp,:)) < gfp_30p(comp));
stdev(comp) = std(squeeze(ica_trial_gfp(comp,good_trials)));
end
gfp_thresholds = gfp_30p + 5*stdev;
rejtrials = [];
for trial=1:eeg.trials
if sum(ica_trial_gfp(:,trial)' > gfp_thresholds) > (num_comp_thresh*num_keepcomps)
rejtrials = [rejtrials trial];
end
end
keeptrials = setdiff([1:eeg.trials],rejtrials);
trial_count = zeros(numel(allowable_values),1);
for trial=1:numel(keeptrials)
epoch = eeg.epoch(keeptrials(trial));
stim = find(ismember(cell2mat(epoch.eventtype),stims));
this_stim = epoch.eventtype{stim};
clear index;
for cond=1:numel(allowable_values)
if [this_stim]==allowable_values{cond};
index = cond; break;
end
end
trial_count(index) = trial_count(index) + 1;
end
clear trial_stats;
trial_stats.subj = subj;
trial_stats.orig_num_trials = eeg.trials;
trial_stats.new_num_trials = numel(keeptrials);
trial_stats.rejtrials = rejtrials;
trial_stats.trial_count = trial_count;
save([outpath 'batch2_summary.mat'],'trial_stats');
marktrials = zeros(1,eeg.trials);
marktrials(rejtrials) = 1;
eeg = pop_rejepoch(eeg,marktrials,0);
eeg = eeg_checkset(eeg);
eeg.setname = [subj '_merged'];
eeg = pop_saveset(eeg, [eeg.setname '.set'], outpath );
end
Reading data in CNT format...
eeg_checkset note: upper time limit (xmax) adjusted so (xmax-xmin)*srate+1 = number of frames
Importing data events...
eeg_checkset note: creating the original event table (EEG.urevent)
eeg_checkset note: re-creating the original event table (EEG.urevent)
readlocs() warning: More columns in the input than expected.
See >> help readlocs
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: coordinate conversion failed
Readlocs: BESA spherical coords. converted, now deleting BESA fields
to avoid confusion (these fields can be exported, though)
Wrong channel structure size, changes ignored
Re-referencing data
pop_epoch():94 epochs selected
Epoching...
pop_epoch():94 epochs generated
pop_epoch(): checking epochs for data discontinuity
pop_rmbase(): Removing baseline...
Reading data in CNT format...
eeg_checkset note: upper time limit (xmax) adjusted so (xmax-xmin)*srate+1 = number of frames
Importing data events...
eeg_checkset note: creating the original event table (EEG.urevent)
eeg_checkset note: re-creating the original event table (EEG.urevent)
readlocs() warning: More columns in the input than expected.
See >> help readlocs
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: coordinate conversion failed
Readlocs: BESA spherical coords. converted, now deleting BESA fields
to avoid confusion (these fields can be exported, though)
Wrong channel structure size, changes ignored
Re-referencing data
pop_epoch():91 epochs selected
Epoching...
pop_epoch():91 epochs generated
pop_epoch(): checking epochs for data discontinuity
pop_rmbase(): Removing baseline...
Reading data in CNT format...
eeg_checkset note: upper time limit (xmax) adjusted so (xmax-xmin)*srate+1 = number of frames
Importing data events...
eeg_checkset note: creating the original event table (EEG.urevent)
eeg_checkset note: re-creating the original event table (EEG.urevent)
readlocs() warning: More columns in the input than expected.
See >> help readlocs
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: Out of range or non-integer values truncated during conversion to character.
Warning: coordinate conversion failed
Readlocs: BESA spherical coords. converted, now deleting BESA fields
to avoid confusion (these fields can be exported, though)
Wrong channel structure size, changes ignored
Re-referencing data
pop_epoch():93 epochs selected
Epoching...
pop_epoch():93 epochs generated
pop_epoch(): checking epochs for data discontinuity
pop_rmbase(): Removing baseline...
Merging datasets...
Merging datasets...
Inserting boundary event...
Concatenating urevents...
Concatenating events...
Reconstituting epoch information...
Merging datasets...
Inserting boundary event...
Concatenating urevents...
Concatenating events...
Reconstituting epoch information...
Undefined function or variable 'corr_threshold'.
Error in ==> batch2 at 41
rejcomps = find(max(cnt_stats.similarity,[],1)> corr_threshold); %cnt_stats.rejcomps;


This glossary defines terms used in Apache Geode documentation.
ACK wait threshold
A time-to-wait for message acknowledgment between system members.
administrative event
See event.
API
Application Programming Interface. Geode provides APIs to cached data for Java applications.
application program
A program designed to perform a specific function directly for the user or, in some cases, for another application program. Geode applications use the Geode application programming interfaces (APIs) to modify cached data.
attribute
Querying: A named member of a data object. The public fields and methods of an object may be accessed as attributes in the context of a query.
Region: See region attributes.
attribute path
A sequence of attributes separated by a dot (.), applied to objects where the value of each attribute is used to apply the next attribute.
blocking
A behavior associated with synchronization functions. Blocking behavior is exhibited as waiting for a signal to proceed, regardless of how long it takes. See also timeout.
cache
In-memory Geode data storage created by an application or cache server for data storage, distribution, and management. This is the point of access for Java applications for all caching features, and the only view of the cache that is available to the application. Cache creation creates a connection to the distributed system. See also local and remote.
cache-local
Residing or occurring in the local cache.
cache.xml
Common name for the XML file that declares the initial configuration of a cache. This file is used to customize the behavior of the Geode cache server process and can be used by any Java application. Applications can also configure the cache through the Geode Java APIs. You can give this file any name.
cache event
See event.
cache listener
User-implemented plug-in for receiving and handling region entry events. A region’s cache listener is called after an entry in the local cache is modified. See also cache writer.
cache loader
User-implemented plug-in for loading data into a region. A region’s cache loader is used to load data that is requested of the region but is not available in the distributed system. For a distributed region, the loader that is used can be in a different cache from the one where the data-request operation originated. See also netSearch and netLoad.cache misses, where a requested key is not present or has a null value in the local cache.
cache miss
The situation where a key’s value is requested from a cache and the requested key is not present or has a null value. Geode responds to cache misses in various ways, depending on the region and system configuration. For example, a client region goes to its servers to satisfy cache misses. A region with local scope uses its data loader to load the value from an outside data source, if a loader is installed on the region.
cache server
A long-lived, configurable Geode distributed system member process that can service client connections.
cache transaction
A native Geode transaction, managed by Geode and not by JTA. This type of transaction operates only on data available from the Geode cache in the local member. See also JTA and global transaction.
cache writer
User-implemented plug-in intended for synchronizing the cache with an outside data source. A region’s cache writer is a synchronous listener to cache data events. The cache writer has the ability to abort a data modification. See also cache listener and netWrite.
client
A Geode application that is configured as a standalone distributed system member, with regions configured as client regions. Client configuration uses the <client-cache> cache.xml
element and the ClientCache API.
client region
A Geode cache region that is configured to go to one or more Geode servers, in a separate Geode distributed system, for all data distribution activities. Among other things, client regions go to servers to satisfy cache misses, distribute data modifications, and to run single queries and continuous queries.
cluster configuration service
The cluster configuration service saves cluster configurations created by gfsh commands to the locators in a cluster and distributes the configurations to members of the cluster.
collection
Used in the context of a query for a group of distinct objects of homogeneous type, referred to as elements. Valid collections include the java.util.Collection
as well as Set, Map, List, and arrays. The elements in a collection can be iterated over. Iteration over a Map traverses its entries as instances of Map.Entry. A region can also be treated as a collection of its values.
commit
A transactional operation that merges a transaction’s result into the cache. Changes are made in an “all or none” fashion. Other changes from outside the current transaction are kept separate from those being committed.
concurrency-level
Region attribute that specifies an estimate of the number of threads ever expected to concurrently modify values in the region. The actual concurrency may vary; this value is used to optimize the allocation of system resources.
conflation
Combining entries in a message queue for better performance. When an event is added to queue, if a similar event exists in the queue, there are two ways to conflate the events. One way is to remove the existing entry from wherever it resides in the queue, and add the new entry to the end of the queue. The other way is to replace the existing entry with the new entry, where it resides in the queue, and add nothing to the end of the queue. In Geode, region entry update events, server events going to clients, and gateway sender events going to remote distributed systems can all be conflated.
connection
The connection used by an application to access a Geode system. A Java application connects to its Geode distributed system when it creates its cache. The application must connect to a distributed system to gain access to the Geode functionalities. A client connects to a running Geode server to distribute data and events between itself and the server tier. These client connections are managed by server connection pools within the client applications. Gateway senders connect to a remote gateway receiver to distribute data events between sites.
consumer
Geode member process that receives data and/or events from other members. Peer consumers are often configured with replicated regions, so all changes in the distributed system arrive into the local cache. Client consumers can register subscriptions with their servers so that updates are automatically forwarded from the server tier. See producer.
coordinator
The member of the distributed system that sends out membership views. This is typically the locator in Geode.
data accessor
In the context of a region, a member configured to use a region, but not store any data for it in the member’s local cache. Common use cases for data accessors are thin clients, and thin producer and consumer applications. Accessors can put data into the region and receive events for the region from remote members or servers, but they store no data in the application. See also data store.
data entry
See entry.
data fabric
Also referred to as an in-memory data grid or an enterprise data fabric. Geode is an implementation of a data fabric. A data fabric is a distributed, memory-based data management platform that uses cluster-wide resources – memory, CPU, network bandwidth, and optionally local disk – to manage application data and application logic (behavior). The data fabric uses dynamic replication and data partitioning techniques to offer continuous availability, very high performance, and linear scalability for data intensive applications, all without compromising on data consistency even when exposed to failure conditions.
data-policy
Region attribute used to determine what events the region receives from remote caches, whether data is stored in the local cache, and whether the data is persisted to disk. For disk persistence, writes are performed according to the cache disk-store configuration.
data region (region)
A logical grouping of data within a cache. Regions usually contain data entries (see entry). Each region has a set of region attributes governing activities such as expiration, distribution, data loading, events, and capacity control. In addition, a region can have an application-defined user attribute.
data store
In the context of a region, a member configured to store data for the region. This is used mostly for partitioned regions, where data is spread across the distributed system among the data stores. See also data accessor.
deadlock
A situation in which two or more processes are waiting indefinitely for events that will never occur.
destroy
Distributed: To remove a cached object across the distributed cache.
Local: To remove a cached object from the local cache only.
disk region
A persistent region.
disk-store
Cache element specifying location and write behavior for disk storage. Used for persistence and overflow of data. The cache can have multiple disk stores, which are specified by name for region attributes, client subscription queues (for servers), and WAN gateway sender queues.
distributed cache
A collection of caches spread across multiple machines and multiple locations that functions as a single cache for the individual applications.
distributed system
One or more Geode system members that have been configured to communicate cache events with each other, forming a single, logical system.
distributed-ack scope
Data distribution setting that causes synchronous distribution operations, which wait for acknowledgment from other caches before continuing. Operations from multiple caches can arrive out of order. This scope is slower but more reliable than distributed-no-ack.
distributed-no-ack-scope
Data distribution setting that causes asynchronous distribution operations, which return without waiting for a response from other caches. This scope produces the best performance, but is prone to race conditions.
entry
A data object in a region consisting of a key and a value. The value is either null (invalid) or a Java object. A region entry knows what region it is in. An entry can have an application-defined user attribute. See also region data, entry key, and entry value.
entry key
The unique identifier for an entry in a region.
entry value
The data contained in an entry.
event
An action recognized by the Geode system members, which can respond by executing callback methods. The Geode API produces two types of events: cache events for detail-level management of applications with data caches and administrative events for higher-level management of the distributed system and its components. An operation can produce administrative events, cache events, or both.
eviction-attributes
Region attribute that causes the cache to limit the size of the region by removing old entries to make space for new ones.
expiration
A cached object expires when its time-to-live or idle timeout counters are exhausted. A region has one set of expiration attributes for itself and one set for all of its entries.
expiration action
The action to be taken when a cached object expires. The expiration action specifies whether the object is to be invalidated or destroyed and whether the action is to be performed only in the local cache or throughout the distributed system. A destroyed object is completely removed from the cache. A region is invalidated by invalidating all entries contained in the region. An entry is invalidated by having its value marked as invalid. Region.getEntry.getValue returns null for an invalid entry.
In Geode, expiration attributes are set at the region level for the region and at the entry level for entries. See also idle timeout and time-to-live.
factory method
An interface for creating an object which at creation time can let its subclasses decide which class to instantiate. The factory method helps instantiate the appropriate subclass by creating the correct object from a group of related classes.
forced disconnect
Forcible removal of a member from membership without the member’s consent.
gateway receiver
A gateway receiver defines connection information for receiving region events that were distributed from a gateway sender in a multi-site deployment.
gateway sender
A gateway sender defines a single remote distributed system site and an associated queue for distributing region events in a multi-site deployment.
gemfire.properties
Common name for the file used for distributed system configuration, including system member connection and communication behavior, logging and statistics files and settings, and security settings. Applications can also configure the distributed system through the Geode Java APIs. You can give this file any name.
global scope
Data distribution setting that provides locking across the distributed system for load, create, put, invalidate, and destroy operations on the region and its entries. This scope is the slowest, but it guarantees consistency across the distributed system.
global transaction
A JTA-controlled transaction in which multiple resources, such as the Geode cache and a JDBC database connection, participate. JTA coordinates the completion of the transaction with each of the transaction’s resources. See also JTA and cache transaction.
HTTP
World Wide Web’s Hypertext Transfer Protocol. A standard protocol used to request and transmit information over the Internet or other computer network.
idle timeout
The amount of time a region or region entry may remain in the cache without being accessed before being expired. Access to an entry includes any get operation and any operation that resets the entry’s time-to-live counter. Region access includes any operation that resets an entry idle timeout and any operation that resets the region’s time-to-live.
Idle timeout attributes are set at the region level for the region and at the entry level for entries. See also time-to-live and expiration action.
initial capacity
Region attribute. The initial capacity of the map used for storing region entries.
invalid
The state of an object when the cache holding it does not have the current value of the object.
invalidate
Distributed: To mark an object as being invalid across the distributed cache.
Local: To mark an object as being invalid in the local cache only.
JDBC
Java DataBase Connectivity. A programming interface that lets Java applications access a database via the SQL language.
JMX
Java Management eXtensions. A set of specifications for dynamic application and network management in the J2EE development and application environment.
JNDI
Java Naming and Directory Interface. An interface to naming and directory services for Java applications. Applications can use JNDI to locate data sources, such as databases to use in global transactions. Geode allows its JNDI to be configured in a cache.xml
configuration file.
JTA
Java Transaction API. The local Java interfaces between a transaction manager (JTS) and the parties involved in a global transaction. Geode can be a member of a JTA global transaction. See also global transaction.
JVM
Java Virtual Machine. A virtual machine capable of handling Java bytecode.
key constraint
Enforcing a specific entry key type. The key-constraint region attribute, when set, constrains the entries in the region to keys of the specified object type.
listener
An event handler. The listener registers its interest in one or more events, such as region entry updates, and is notified when the events occur.
load factor
Region attribute. The load factor of the map used for storing entries.
local
Local cache: The part of the distributed cache that is resident in the current member’s memory. This term is used to differentiate the cache where a specific operation is being performed from other caches in the same distributed system or in another distributed system. See also remote.
Region with local scope: A region whose scope is set to local. This type of region does not distribute anything with other members in the distributed system.
Region shortcuts: In the RegionShortcut and settings, LOCAL means the scope is set to local. All client regions have local scope. In the ClientRegionShortcut settings, LOCAL means the region does not connect to the client’s servers.
local scope
Data distribution setting that keeps data private and visible only to threads running within the local member. A region with local scope is completely contained in the local cache. Client regions are automatically given local scope.
locator
Geode process that tracks system members and provides current membership information to joining members so they can establish communication. For server systems, the locator also tracks servers and server load and, when a client requests a server connection, the locator sends the client to one of the least loaded servers. .
LRU
Least recently used. Used to refer to region entry or entries most eligible for eviction due to lack of interest by client applications. Geode offers eviction controllers that use the LRU status of a region’s entries to determine which to evict to free up space. Possible eviction actions are local destroy and overflow. See also resource manager.
machine
Any Geode-supported physical machine or Virtual Machine.
member
A process that has defined a connection to a Geode distributed system and created a Geode cache. This can be a Java or Native Client application. This can also be a Geode process such as a locator or cacheserver. The minimal Geode process configuration is a single member that is connected to a distributed system.
message queue
A first-in, first-out data structure in a Geode system member that stores messages for distribution in the same order that the original operations happened in the local member. Each thread has its own queue. Depending on the kind of queue, the messages could be going between two members of a distributed system, a client and server, or two members in different distributed systems. See also conflation.
mirroring
See replicate.
multicast
A form of UDP communications where a datagram is sent to multiple processes in one network operation.
named region attributes
Region attributes that are stored in the member memory and can be retrieved through their region attributes refid setting. Geode provides standard predefined named region attributes, that are stored using region shortcut refids. You can use any stored attributes that you wish, setting an id when you create them and using the id setting in the refid you want to use to retrieve them.
netLoad
The method used by Geode to load an entry value into a distributed region. The netLoad operation invokes all remote cache loaders defined for the region until either the entry value is successfully loaded or all loaders have been tried.
netSearch
The method used by Geode to search remote caches for a data entry that is not found in the member’s local cache region. This method operates only on distributed regions with a data-policy of empty, normal and preloaded.
netWrite
The method used by Geode to invoke a cache writer for region and region entry events. This method operates only on distributed regions. For each event, if any cache writer is defined for the region, the netWrite operation invokes exactly one of them.
network partitioning
A situation that arises from a communications partition that causes processes to become unaware of one another.
OQL
Object Query Language, SQL-92 extended for querying object data. Geode supports a subset of OQL.
off-heap memory
Memory that is not on the standard Java heap and that is not managed by the JVM and its garbage collector.
overflow
Eviction option for eviction controllers. This causes the values of LRU entries to be moved to disk when the region reaches capacity. Writes are performed according to the cache disk-store configuration.
oplog / operation log
The files in a disk-store used for the cache operations.
partition
The memory in each member that is reserved for a specific partitioned region’s use.
partitioned region
A region that manages large volumes of data by partitioning it into manageable chunks and distributing it across multiple machines. Defining partition attributes or setting the region attribute data-policy to partition makes the region a partitioned region.
peer
A Geode member application that is not configured as a client. Peer configuration uses the <cache> cache.xml
element and the Cache API. Peers can also be configured as servers to client applications and as gateway-receivers or gateway-senders to remote distributed systems.
persistent region
A region with the attribute data-policy set to persistent-replicate.
persistent-partition
A region attribute setting identifying a region as a partitioned region whose data is persisted to disk. With persistence, all region entry keys and values are stored in an operation log on disk as well as being stored in memory. Also referred to as disk region. Writes are performed according to the cache disk-store configuration.
persistent-replicate
A region attribute setting identifying a region as a replicate whose data is persisted to disk. With persistence, all region entry keys and values are stored in an operation log on disk as well as being stored in memory. Also referred to as disk region. Writes are performed according to the cache disk-store configuration.
producer
A Geode member process that puts data into the cache for consumption by other members. Producers may be configured with empty regions, where the data they put into the cache is not stored locally, but causes cache update events to be sent to other members. This is a common configuration in peer members and for client processes. See consumer.
pull model
Data distribution model where each process receives updates only for the data in which the process has explicitly expressed interest. In a Geode peer member, this is accomplished using a distributed, non-replicated region and creating the data entries that are of interest in the local region. When updates happen for the region in remote caches, the only updates that are forwarded to the local cache are those for entries that are already defined in the local cache. In a Geode client, you get pull behavior by specifically subscribing to the entries of interest. See push model.
push model
Data distribution model where each process receives updates for everything in the data set. In a Geode peer member, this is accomplished using a replicated region. All data modifications, creations, and deletes in remote caches are pushed to the replicated region. In a Geode client, you get push behavior by registering interest in all keys in the region. See pull model.
query string
A fully-formed SQL statement that can be passed to a query engine and executed against a data set. A query string may or may not contain a SELECT statement.
race condition
Anomalous behavior caused by the unexpected dependence on the relative timing of events. Race conditions often result from incorrect assumptions about possible ordering of events.
range-index
An XPath index optimized for range-queries with the added index maintenance expense of sorting the set of values. A range index allows faster retrieval of the set of nodes with values in a certain range. See also structure-index and value-index.
region
A logical grouping of data within a cache. Regions usually contain data entries (see entry). Each region has a set of region attributes governing activities such as expiration, distribution, data loading, events, and capacity control. In addition, a region can have an application-defined user attribute.
region attributes
The class of attributes governing the creation, distribution, and management of a region and its entries.
region data
All of the entries directly contained in the region.
region entry
See entry.
region shortcut
Enums RegionShortcut and ClientRegionShortcut defining the main region types in Geode for peers/servers and clients, respectively. Region shortcuts are predefined named region attributes.
remote
Resident or running in a cache other than the current member’s cache, but connected to the current member’s cache through Geode. For example, if a member does not have a data entry in the region in its local cache, it can do a netSearch in an attempt to retrieve the entry from the region in a remote cache within the same distributed system. Or, if the member is a client, it can send a request to a server in an attempt to retrieve the entry from the region in a remote server cache in the server’s distributed system. In multi-site installations, a gateway sends events from the local cache to remote caches in other distributed systems. See also local.
replicated region
A region with data-policy set to replicate or persistent-replicate.
replicate
Region data-policy specification indicating to copy all distributed region data into the local cache at region creation time and to keep the local cache consistent with the distributed region data.
resource manager
Geode process that works with your JVM’s tenured garbage collection (GC) to control heap use and protect your JVM from hangs and crashes due to memory overload. The manager prevents the cache from consuming too much memory by evicting old data and, if the collector is unable to keep up, by refusing additions to the cache until the collector has freed an adequate amount of memory. Eviction is done for regions configured for LRU eviction based on heap percentage. See also LRU and eviction-attributes.
rollback
A transactional operation that excludes a transaction’s changes from the cache, leaving the cache undisturbed.
scope
Region attribute: In non-partitioned regions, a distribution property for data identifying whether it is distributed and, if so, whether distribution acknowledgements are required and whether distributed synchronization is required. A distributed region’s cache loader and cache writer (defined in the local cache) can be invoked for operations originating in remote caches. A region that is not distributed has a local scope. See also replicate.
Querying: The data context for the part of the query currently under evaluation. The expressions in a SELECT statement’s FROM clause can add to the data that is in scope in the query.
SELECT statement
A statement of the form SELECT projection_list FROM expressions WHERE expressions that can be passed to the query engine, parsed, and executed against data in the local cache.
serialization
The process of converting an object or object graph to a stream of bytes.
server
A Geode member application that is configured as a peer in its own system and as a server to connecting Geode client applications.
server group
An optional logical grouping of servers in a server distributed system. There is always the default server group made up of all available server in the server distributed system. Clients can specify the server group in their server pool configuration. Then the pool only connects to those servers. If no group is specified, the default is used.
server connection pool
The cache entity that manages client connections to servers.
socket
The application interface for TCP/IP communications. UDP provides unicast and multicast datagram sockets, while TCP provides server and connection sockets. TCP server sockets are used by server processes to create connection sockets between the server and a client.
SQL
Structured Query Language.
SSL
Secure Socket Layer. A protocol for secure communication between Java VMs.
standalone distributed system
A distributed system configured for no communication with peers. Client applications are generally defined with standalone distributed systems, so there is no peer communication and all event and data communication is done between the client member and the server tier.
statistics enabled
Region attribute. Specifies whether to collect statistics for the region.
struct
A data type that has a fixed number of elements, each of which has a field name and can contain an object value.
structure-index
An XPath index that is basically a pre-computed query. Any legal XPath expression can be used. The index maintains lists of all nodes that match the expression used to create it. If a query is performed that has the same expression as the index then the result is available without XPath evaluation. See also range-index and value-index.
system member
See member.
TCP
The Transmission Control Protocol is a part of the internet protocol (IP) suite that provides unicast communications with guaranteed delivery. The TCP protocol is connection-based, meaning that a TCP socket can only be used to send messages between one pair of processes at a time. Compare to UDP.
timeout
A behavior associated with synchronization functions. Timeout behavior is exhibited as refusal to wait longer than a specified time for a signal to proceed. See also blocking.
time-to-live
The amount of time a region or region entry may remain in the cache without being modified before being expired. Entry modification includes creation, update, and removal. Region modification includes creation, update, or removal of the region or of any of its entries.
Time-to-live attributes are set at the region level for the region and at the entry level for entries. See also idle timeout and expiration action.
transaction
See cache transaction and global transaction.
transaction listener
User-implemented plug-in for receiving and handling transaction events. A transaction listener is called after a transaction commits. See also transaction writer.
transaction writer
User-implemented plug-in intended for synchronizing the cache with an outside data source. A transaction writer is a synchronous listener to cache transactions. The transaction writer has the ability to veto a transaction. See also transaction listener.
transactional view
The result of a history of transactional operations for a given open transaction.
transport layer
The network used to connect the Geode system members in a Geode system.
TTL
See time-to-live.
UDP
The User Datagram Protocol is a part of the internet protocol (IP) suite that provides simple, unreliable transmission of datagram messages from one process to another. Reliability must be implemented by applications using UDP. The UDP protocol is connectionless, meaning that the same UDP socket can be used to send or receive messages to or from more than one process. Compare to TCP.
unicast
A message sent from one process to another process (point-to-point communications). Both UDP and TCP provide unicast messaging.
URI
Uniform Resource Identifier. A unique identifier for abstract or physical resources on the World Wide Web.
user attribute
An optional object associated with a region or a data entry where an application can store data about the region or entry. The data is accessed by the application only. Geode does not use these attributes. Compare to region attributes, which are used by Geode.
value constraint
Enforcing a specific entry value type. The value-constraint region attribute, when set, constrains the entries in the region to values of the specified object type. Value constraints can be used to provide object typing for region querying and indexing. The value-constraint is only checked in the cache that does the entry put or create operation. When the entry is distributed to other caches, the value constraint is not checked.
value-index
An XPath index that operates much as a structure-index does, but that separates the nodes that match the XPath expression into sets mapped by each node’s value. This allows further filtering of the nodes to be evaluated in a query by going directly to those with a specific value. See also structure-index and range-index.
view
A collection of member identifiers that defines the membership group.
Virtual Machine
A completely isolated operating system installation within your normal operating system. This is generally implemented by software emulation or hardware virtualization.
VMware virtual machine
Also referred to as a VMware VM. A VMware VM is a tightly isolated software container that can run its own operating systems and applications as if it were a physical computer. A VMware VM behaves exactly like a physical computer and contains it own virtual (ie, software-based) CPU, RAM hard disk and network interface card (NIC). An operating system can’t tell the difference between a VMware VM and a physical machine, nor can applications or other computers on a network. Even the VMware VM thinks it is a “real” computer. Nevertheless, a VMware VM is composed entirely of software and contains no hardware components whatsoever.
XML
EXtensible Markup Language. An open standard for describing data, XML is a markup language similar to HTML. Both are designed to describe and transform data, but where HTML uses predefined tags, XML allows tags to be defined inside the XML document itself. Thus, virtually any data item can be identified. The XML programmer creates and implements data-appropriate tags whose syntax is defined in a DTD file or an XSD (XML schema definition.)
XML schema definition
The definition of the structure, content, and semantics used in an XML document. The definition can be used to verify that each item of content in a document adheres to the specification of the element in which the content is placed. The XML schema is a superset of DTD. Unlike DTD, XML schemas are written in XML syntax, which, although more verbose than DTD, are more descriptive and can have stronger typing. Files containing XML schema definitions generally have the XSD extension.
XPath
A language that describes a way to locate and process items in Extensible Markup Language (XML) documents by using an addressing syntax based on a path through the document’s logical structure or hierarchy.
XSD
See XML schema definition.


The Windows client sits in the taskbar when its running and allows you to quickly post entries throughout the day. It also allows you to auto-detect the music playing on your computer. You can even use the Microsoft Word spell checker if Word is installed or add blog entries to Microsoft Outlook.
This version includes a slightly new theme, Outlook integration is back, and runs on .NET framework 3.5. Tagging was also introduced into the client. It works just like the online form with spaces or commas separating tags. You can turn on the music detection feature in options. At this time, it only ships as a 32bit program, but can run on 64bit Vista. Released May 29, 2009.
Windows 7, Vista, XP Client zip
The Windows clients require the .NET framework 2.0. You can get it from Microsoft Windows Update (in XP or 2000) if you do not have it. Version 1.6 released on January 15, 2007. The Outlook integration feature was removed.


Do the following to install necessary dependencies and start development server
In the project directory, you can run:
$ npm install
$ npm start
This project contains source code for my blog in which I talk about making API requests using React JS.
Click here to read my blog


{% extends 'base.html' %} {% block title %} Terms of Service {% endblock title %} {% block header %} Terms of Service {% endblock header %} {% block content %}
By using this site and its associated services, you agree to respect both the community and the services provided by me to it.
You don't have to be an annointed saint or have passed the world's greatest finishing school with the highest possible marks, but you do need to treat other users with respect, and to use the services provided responsibly. This includes avoiding content that others may find offensive, including, but not limited to, profanity and pornography.
Since the nature of what is and is not acceptable is inherently subjective, and since I have not hired a lawyer to spell out in impenetrable legalese exactly where that line is drawn here, in all but the most egregious breaches of the "community norms" you can expect to first be warned before any more punitive measures are taken.
Despite the informal nature of this Terms of Service agreement, I reserve the right to suspend or revoke your access to this site and any or all of its associated services for any reason whatsoever. I don't want to have to do that, though, so please don't make me.
{% endblock content %}


| PostgreSQL 9.0.10 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Chapter 18. Server Configuration | Next |
All parameter names are case-insensitive. Every parameter takes a value of one of five types: Boolean, integer, floating point, string or enum. Boolean values can be written as on, off, true, false, yes, no, 1, 0 (all case-insensitive) or any unambiguous prefix of these.
Some settings specify a memory or time value. Each of these has an implicit unit, which is either kilobytes, blocks (typically eight kilobytes), milliseconds, seconds, or minutes. Default units can be found by referencing pg_settings.unit. For convenience, a different unit can also be specified explicitly. Valid memory units are kB (kilobytes), MB (megabytes), and GB (gigabytes); valid time units are ms (milliseconds), s (seconds), min (minutes), h (hours), and d (days). Note that the multiplier for memory units is 1024, not 1000.
Parameters of type "enum" are specified in the same way as string parameters, but are restricted to a limited set of values. The allowed values can be found from pg_settings.enumvals. Enum parameter values are case-insensitive.
One way to set these parameters is to edit the file postgresql.conf, which is normally kept in the data directory. (A default copy is installed there when the database cluster directory is initialized.) An example of what this file might look like is:
# This is a comment log_connections = yes log_destination = 'syslog' search_path = '"$user", public' shared_buffers = 128MB
One parameter is specified per line. The equal sign between name and value is optional. Whitespace is insignificant and blank lines are ignored. Hash marks (#) designate the rest of the line as a comment. Parameter values that are not simple identifiers or numbers must be single-quoted. To embed a single quote in a parameter value, write either two quotes (preferred) or backslash-quote.
In addition to parameter settings, the postgresql.conf file can contain include directives, which specify another file to read and process as if it were inserted into the configuration file at this point. Include directives simply look like:
include 'filename'
If the file name is not an absolute path, it is taken as relative to the directory containing the referencing configuration file. Inclusions can be nested.
The configuration file is reread whenever the main server process receives a SIGHUP signal (which is most easily sent by means of pg_ctl reload). The main server process also propagates this signal to all currently running server processes so that existing sessions also get the new value. Alternatively, you can send the signal to a single server process directly. Some parameters can only be set at server start; any changes to their entries in the configuration file will be ignored until the server is restarted.
A second way to set these configuration parameters is to give them as a command-line option to the postgres command, such as:
postgres -c log_connections=yes -c log_destination='syslog'
Command-line options override any conflicting settings in postgresql.conf. Note that this means you won't be able to change the value on-the-fly by editing postgresql.conf, so while the command-line method might be convenient, it can cost you flexibility later.
 The environment variable PGOPTIONS can be used for this purpose on the client side:
env PGOPTIONS='-c geqo=off' psql
(This works for any libpq-based client application, not just psql.) Note that this won't work for parameters that are fixed when the server is started or that must be specified in postgresql.conf.
Furthermore, it is possible to assign a set of parameter settings to a user or a database. Whenever a session is started, the default settings for the user and database involved are loaded. The commands ALTER USER and ALTER DATABASE, respectively, are used to configure these settings. Per-database settings override anything received from the postgres command-line or the configuration file, and in turn are overridden by per-user settings; both are overridden by per-session settings.
Some parameters can be changed in individual SQL sessions with the SET command, for example:
SET ENABLE_SEQSCAN TO OFF;
If SET is allowed, it overrides all other sources of values for the parameter. Some parameters cannot be changed via SET: for example, if they control behavior that cannot be changed without restarting the entire PostgreSQL server. Also, some SET or ALTER parameter modifications require superuser permission.
The SHOW command allows inspection of the current values of all parameters.
The virtual table pg_settings (described in Section 45.55) also allows displaying and updating session run-time parameters. It is equivalent to SHOW and SET, but can be more convenient to use because it can be joined with other tables, or selected from using any desired selection condition. It also contains more information about what values are allowed for the parameters.


Properties
Protected $boundOnEnterFrame
$boundOnEnterFrame: function
Protected $events
$events: Object
Protected $paused
$paused: boolean = true
Protected $shouldSaveProps
$shouldSaveProps: boolean = true
Protected $stepIndex
$stepIndex: number = 0
Protected $stepPosition
$stepPosition: number = 0
Protected $stepProps
$stepProps: Array<Object> = []
loop
loop: boolean = false
Static Private $tweens
$tweens
: Array<Tween> = []


My
Diary
Home
About
MyDiary V1 is an online journal where users can pen down their thoughts and feelings.
Functionalities and features
Users can create an account.
User can sign in.
Users can view all entries to their diary.
Users can view the contents of a diary entry.
Users can add entry.
Users can modify an entry.
Users can delete an entry
Users can set and get daily notifications that prompt them to add an entry to their diary.
Any Question?Shoot it to us below..


option group e.g. #ProductIntel
7) Ensure your wwX and userid are the same as Mals (TIP! enter your details at the top before copying example)
8) Open the web page in a browser e.g. Chrome and test it
--- Customize ---
The script looks for an element with id called malsRunningTotal to display the total (if selected). Put this wherever you like within the form and style using CSS.
Total: $0.00
--- Calling Script ---
The script is very versatile. You can activate it on one or more forms (or links) easily. Note: if you don't know jQuery selectors visit https://www.w3schools.com/jquery/jquery_selectors.asp
- Example 1 = specific form by id
MalsScripts.generateOptions('#form1');
This will activate the script on the form with id="form1"
- Example 2 = specific forms by id including price options **** RECOMMENDED ****
MalsScripts.generateOptions('#form1',true);
This will activate the script on the form with id="form1" and display running price
- Example 3 = callback function
MalsScripts.generateOptions('#form1',true,function(){
// Called when script is called;
});
- Example 4 = callback click function
generateOptions('#form1',true,,function(){
// Called when option changed
})
--- General Notes ---
- Add class .mals-ignore to any forms you don't want transformed e.g.


TeenHub was founded last year by the Rockville-Montgomery Robotics Association, Inc., an IRS-recognized non-profit organization that fields FTC Team 5421. Interested in increasing programming literacy in their local community, TeenHub focuses on teaching Python and HTML basics in a monthly/bi-monthly workshop-style at local libraries.
Thanks for stopping by! This page is under construction. Please come back later to see the updated content.


Enumerable Methods
The map method
July 12, 2015
This week at Dev Bootcamp we learned a ton about enumerable methods. Enumerable methods are useful because they give you a lot of ways of doing something to every element of a collection of objects (array, hash, etc.). In this blog post I will be explaining how to utilize the enumerable map method. I chose to elaborate on this method because I found myself using it a lot and it also doubles for an explanation of the enumerable method collect.
 In ruby #map and #collect do exactly the same thing, however it is probably considered better ruby convention to use the #map method. To think of it in the simplest terms the map method is a re-mapping of your original objects through a transformation that occurs when you use #map. Map can be called in its' destructive (!) or non destructive form. If it called using map!, the objects will be transformed permanently.
For an example, lets say you want to multiply each number in an array by 2.