Trends in precipitation and extreme occurrence were analyzed for five locations across Canada using the Canadian Regional Climate Model. Results from the model’s base simulation were compared to those from a future scenario of increased atmospheric CO2. The climatology of nearby weather stations was used to assess the model’s ability to simulate the present and future climate. Other parameters such as 850 and 500 hPa geopotential associated with the most extreme events were analyzed to infer changes in the mechanisms causing such events. The model underestimates annual precipitation along with extreme occurrence and intensity. A wetter, but more variable climate is projected for most locations. Frequency and intensity of extreme events increases at most locations. Simulated extreme events over western locations were found to be associated with cold lows, while eastern events were linked with moisture transport at 850 hPa. Western events were reproduced accurately, whereas eastern ones were not.

Trends in precipitation and extreme occurrence were analyzed for five locations across Canada using the Canadian Regional Climate Model. Results from the model’s base simulation were compared to those from a future scenario of increased atmospheric CO2. The climatology of nearby weather stations was used to assess the model’s ability to simulate the present and future climate. Other parameters such as 850 and 500 hPa geopotential associated with the most extreme events were analyzed to infer changes in the mechanisms causing such events. The model underestimates annual precipitation along with extreme occurrence and intensity. A wetter, but more variable climate is projected for most locations. Frequency and intensity of extreme events increases at most locations. Simulated extreme events over western locations were found to be associated with cold lows, while eastern events were linked with moisture transport at 850 hPa. Western events were reproduced accurately, whereas eastern ones were not.

Thesis (J.C.L.)--Catholic University of America, 1999. / Includes bibliographical references (leaves 70-76).

published_or_final_version / Statistics and Actuarial Science / Doctoral / Doctor of Philosophy

In numerous regions around the globe, climate change can be expected to change the pattern of severe weather events. Migration flows have been systematically larger the higher the proportion of the population in urban areas in the destination county relative to the origin county. Richer models demonstrate that the effects of a number of different types of extreme weather events (i.e. flooding, heat waves, and wildfires) in the origin county on county-to-county migration flows are statistically significantly greater when the destination county is more urbanized. The effect of the number of fatalities from flooding and heat waves in the origin county on migration flows is also amplified when the destination county is more urbanized. Thus it appears that even in a developed country like the U.S. extreme weather events still exacerbate rural-to-urban migration flows.

No description available.

<p>The biggest field in the recent decade in software development has been a subject known as Agile Development. In Agile development the construction of the software is an iterative process and is done with close contact with the costumer. One of the most well-known agile methods is Extreme Programming, which suggests a number of practices to develop software. One of those practices is test-Driven Development, which is the writing of the test code before you write the actual code. This means that one can test the code after it is finished. This creates an opportunity to change the design of the code and then test it again with your test code and discover if any functionality has been lost. The purpose of refactoring is the improvement of the design of existing code. How refactoring affects the performance is not widely discussed and therefore this thesis is going to examine that field. Code examples with and without refactoring principles have been tested. The investigation has been divided into two parts, part one tests individual refactoring principles and part two tests a test application. There are many opinions how to interpret the results of a performance test. After an extensive investigation the arithmetic mean was chosen, mainly because it reflects the total runtime for a series of executions. To test the hypothesis that total execution time will change with refactoring the Students t-test was used. It was chosen because it can be applied even when the variance is unknown. The results were clear, the arithmetic mean increased in five out of six refactoring principles. The test application also increased, but with only 4 %. The reason for the small increase was that it is not possible to go from a non refactored application to a fully refactored application. Another reason is that is was developed with Swedish Rail Administration’s framework which of course was not refactored. The conclusion of this thesis was that one should be careful with refactoring the parts of the code that is executed the most. One should have the “90-10 rule” in mind, it states that 90 % of the execution time is done in 10 % of the code. Another important aspect is that very often is an existing framework used, if you only refactor the new code and not the framework it leads to that only a subset of the code is being refactored. This means that the application does not get fully refactored and therefore the consequences of the refactoring mitigates.</p>

No description available.

The biggest field in the recent decade in software development has been a subject known as Agile Development. In Agile development the construction of the software is an iterative process and is done with close contact with the costumer. One of the most well-known agile methods is Extreme Programming, which suggests a number of practices to develop software. One of those practices is test-Driven Development, which is the writing of the test code before you write the actual code. This means that one can test the code after it is finished. This creates an opportunity to change the design of the code and then test it again with your test code and discover if any functionality has been lost. The purpose of refactoring is the improvement of the design of existing code. How refactoring affects the performance is not widely discussed and therefore this thesis is going to examine that field. Code examples with and without refactoring principles have been tested. The investigation has been divided into two parts, part one tests individual refactoring principles and part two tests a test application. There are many opinions how to interpret the results of a performance test. After an extensive investigation the arithmetic mean was chosen, mainly because it reflects the total runtime for a series of executions. To test the hypothesis that total execution time will change with refactoring the Students t-test was used. It was chosen because it can be applied even when the variance is unknown. The results were clear, the arithmetic mean increased in five out of six refactoring principles. The test application also increased, but with only 4 %. The reason for the small increase was that it is not possible to go from a non refactored application to a fully refactored application. Another reason is that is was developed with Swedish Rail Administration’s framework which of course was not refactored. The conclusion of this thesis was that one should be careful with refactoring the parts of the code that is executed the most. One should have the “90-10 rule” in mind, it states that 90 % of the execution time is done in 10 % of the code. Another important aspect is that very often is an existing framework used, if you only refactor the new code and not the framework it leads to that only a subset of the code is being refactored. This means that the application does not get fully refactored and therefore the consequences of the refactoring mitigates.

Thesis (Ph. D.)--Ohio State University, 2003. / Title from first page of PDF file. Document formatted into pages; contains x, 81 p.; also includes graphics (some col.). Includes abstract and vita. Advisor: Bostwick Wyman, Dept. of Mathematics. Includes bibliographical references (p. 80-81).