text:
Glenn et al,
Now i am becoming annoyed. I enjoy the exchanges & am learning much. But this asinine stabbing @ each other does nothing to add to the discussion. My kids would be getting a sharp word and a time out @ this point. Randy did NOT deserve this email below. Period.
Sent from Nokia E75
-original message-
Subject: Re: [asa] Data doesn't support global warming
From: "Glenn Morton" <firstname.lastname@example.com>
Date: 21/12/2009 12:50 PM
4th post today replies to Randy and to Rich.
Randy wrote:
> To be honest, Glenn, my eyes are blurry and my head is spinning from
> scanning through the last couple of hundred posts you all put up in the
> last
> week. So forgive me for not answering your question until I get a chance
> to
> think it about further. Yes, after reading through the exchanges between
> you
> and Rich, I understood what you were saying much better and would have
> withdrawn my note. You're questioning both the data and the
> interpretation.
> I really appreciate the way you and Rich are getting into the data, though
> you both use more gratuitous jabs at each other and subjective
> descriptions
> of others than I like. In his post John Walley noted "I know Chuck Colson
> is
> openly derided on the ASA list ..." I hope he isn't correct, I don't know
> when that happened, if it did. But NO ONE should ever be "openly derided"
> on
> this list. Can't we all pay attention and focus on debating ideas WITHOUT
> deriding anyone who might hold to those ideas?
> Now I have to give my eyes and brain a rest.
> Randy
Randy, I am sorry, it is simply not credible that you can't understand what
is being asked. Even with tired eyes and a tired head, it isn't too
difficult to conclude that an air conditioner heat exhaust next to a
thermometer might bias the thermometer. Frankly, I am extremely disappointed
in your response. That one is a real no brainer. Do you think that an air
conditioner heat exchanger will COOL the thermometer as it out puts hot air?
Is that really what you think? Have you ever put your hand into the wind
stream coming out of an air conditioner exhaust? did it feel COOL????? I
doubt it seriously. Was that not clear that this is the hot end of the
airconditioner system, not the cold end? Remember Randy, we have an
obligation as Christians to uphold truth.
But unfortunately from what I had heard about your role in these debates,
that is about what I expected. I have been told that you seem incapable of
criticising anything in the theory of global warming. Scientists should be
able to criticize even what they believe. They should be able to know the
weaknesses of what they believe.
Maybe tomorrow after a nights rest you can comment on whether or not a
thermometer next to an AC heat exchanger might bias the result. Take some
vitamins and it might help your decision making processes. Do you think
that would be too difficult for you? I wouldn't want to tax you too much.
It is truly amazing to me that global warming advocates won't condemn such
sloppy scientific practices. In fact it disgusts me. It seems to put
political beliefs above data and good logic
Rich wrote in the Three of the For hottest years thread:
>>>GISS posted their maps and graphs for the year a couple days ago. The
>>>diagnosis: three of the four hottest years in the instrumental record
>>>happened in the last half decade.
2009 comes in at number 4 missing number 2 by .01 degrees C. All-time record
high November. Map here comparing to number 1 (2005) and number 2 (2007).
Yep air conditioners next to thermometers helps that, especially given that
in 1900 there were no air conditioners out there but in 2009 they were
everywhere. This seems to be too difficult a concept for AGW advocates to
grapple with but it shouldn't be.
Rich wrote in this thread.
> ----- Original Message -----
> From: Rich Blinne
> To: Glenn Morton ; John Walley ; Randy Isaac
> Cc: asa
> Sent: Sunday, December 20, 2009 7:28 PM
> Subject: [asa] Data doesn't support global warming
> Yes, the god-like climatologists with that specialist capability called
> "reading comprehension". More on that later. First of all why quote TAR
> which came out in 2001 when AR4 came out in 2007? But anyway, let's dive
> in here. Here's the figure that Glenn references:\
Rich if you didn't notice I did quote the fourth report this morning when I
compared it to the third. The thing that you can't seem to understand is
that in order to show that the thermal history of the climate has changed,
one MUST compare older reports with
modern ones. The note to which you are replying is comparing the present
NOAA temperature anomaly with the AR3. If the past history is changed
between them, I know no other way to show that than to cite SOME older
Of course you can't stand to see any criticism of your religion.
> http://www.grida.no/climate/ipcc_tar/wg1/images/fig2-1.gif
> Figure 2.1: (a) Annual anomalies of global average land-surface air
> temperature (oC), 1861 to 2000, relative to 1961 to 1990 values. Bars and
> solid curve are from CRU (Jones et al., 2001). Values are the simple
> average of the anomalies for the two hemispheres. The smoothed curve was
> created using a 21-point binomial filter giving near decadal averages. (b)
> As (a) but smoothed curves only from NCDC (updated from Peterson and Vose,
> 1997) – thin solid curve; GISS (adapted from Hansen et al., 1999) – thick
> dashed curve; SHI (updated from Vinnikov et al., 1990) – thin dashed curve
> to 1999 only; Peterson and Vose (1997) – thin solid curve. Thick solid
> curve – as in (a). Two standard error uncertainties are centred on the CRU
> curve and are estimated using an optimum averaging method (Folland et al.,
> 2001) [RDB Note: Folland et al can be found here
> http://www.agu.org/pubs/crossref/2001/2001GL012877.shtml] and include
> uncertainties due to urbanisation but not due to uncertain- ties in
> thermometer exposures. The NCDC curve is the weighted average of the two
> hemispheres according to the area sampled, which accounts for most of the
> differences from the CRU curve.
Wow, Rich, you can copy a caption and link to a figure. I am soooooo
> John, note the different averaging techniques and how it gives a slightly
> different answer with both averages inside the error bars. Now to the
> graph from the technical summary.
> http://www.grida.no/climate/ipcc_tar/wg1/images/figts-2.gif
> It's caption:
> Figure 2: Combined annual land-surface air and sea surface temperature
> anomalies (°C) 1861 to 2000, relative to 1961 to 1990. Two standard error
> uncertainties are shown as bars on the annual number. [Based on Figure
> 2.7c]
Again you show the amazing ability to copy a caption. I think I provided
my readers with the information that both pictures are anomalies with regard
to 1961-1990. Thanks for verifying this.
> So we go back to the graph referenced by Glenn. Uh, wait a minute!!! Glenn
> referenced Figure 2.1a and the report referenced Figure 2.7c. At least
> Glenn didn't expunge the incriminating evidence in his picture and if he
> was going to refer to Figure 2.1 it should be Figure 2.1b. Glenn
> apparently has trouble reading captions. What's Figure 2.7c?
> http://www.grida.no/climate/ipcc_tar/wg1/images/fig2-7.gif
> Figure 2.7: Smoothed annual anomalies of combined land-surface air and sea
> surface temperatures (°C), 1861 to 2000, relative to 1961 to 1990, for (a)
> Northern Hemisphere; (b) Southern Hemisphere; and (c) Globe. The smoothed
> curves were created using a 21-point binomial filter giving near-decadal
> averages. Optimally averaged anomalies (Folland et al., 2001) - solid
> curves; standard area weighted anomalies (adapted from Jones et al.,
> 2001) - dashed curves. Also shown are the unsmoothed optimum averages -
> red bars, and twice their standard errors - width denoted by black "I".
> Note that optimum averages for the Southern Hemisphere are a little warmer
> before 1940, when the data are sparse, than the area-weighted averages.
> However, the two types of averaging give similar resoults [sic] in the
> Northern Hemisphere.
> Figure 2.1a that Glenn referenced is the simple area average from Jones et
> al 2001 and as we see from the caption to Figure 2.7(c) corresponds to the
> dashed curves. It's a match. What about the technical summary graph? It
> matches the optimal average calculation from Folland et al 2001 and the
> solid curve. No history was changed. Just two different ways to make the
> calculation.
Ridiculous Rich, (that may catch on as a moniker), I showed the
differences in the pictures. With circles and arrows. Maybe you can't see
circles and arrows or see that two curves don't match. That is truly sad.
But if two different methodologies say that the history was different, that
IS changing history if one relies on one vs the other. Why shouldn't we
just use what was observed? After all that is what science is all
about--what is observed.
Rich, if no history was changed, please explain why in one picture the
coldest year was 1910 and in the other it was 1890. REAL history requires
that one or the other be coldest (or that they both be equal). But neither
of the two methods show them equal. One shows 1890 as the coldest and the
other shows 1910. Can you not even acknowledge that 1910 is not 1890?
Here is that picture
Someone told me that you had never ever granted a single acknowledgement
that a single criticism of global warming is valid. That is very
interesting to me as it seems to indicate that you think global warming
theory is perfection itself, no improvement is possible. I of course think
all theories have room for improvement and criticism. So, is it your
contention that there is absolutely nothing that can be criticised about
AGW? If that is false, what do you think is criticizable about global
>>>That's how the IPCC process works. <<<
Really? It uses different methods to come up with whatever answer it
prefers? It uses different methods and comes up with different histories?
So how in the H can we say that this is all settled? They don't even know
what the historical temperature was!
Here again is the comparison of NOAA with IPCC 2001 which shows that they
have different histories.
Notice again, my dear Rich that the coldest year in the IPCC is 1890 if that
true, then NOAA's claim to have the coldest temperature in 1910 can't be
true. One or the other of these pictures is wrong. Which one is it and why
do you pick one over the other?
Rich, the error bars are so large that one should not yet have even measured
the global warming of .84 deg C above the noise level. when I compare the
temperatures between two nearby towns, the standard deviation for towns less
than 25 miles apart is usually about 3 degrees F Or approximately 1.5 deg C.
Rich, your email was entirely a red herring. I care less about what the
'evil climatologists' conclude as to the amount of warming than you do. I
care if their methodologies for concluding what they do are sound. You are
anything but a serious
scientist. Why, I might think you are an engineer. But I do admire your
ability to bully people. That is a very useful skill.
To unsubscribe, send a message to firstname.lastname@example.com with
"unsubscribe asa" (no quotes) as the body of the message.
To unsubscribe, send a message to firstname.lastname@example.com with
"unsubscribe asa" (no quotes) as the body of the message.
Received on Sun Dec 20 23:15:18 2009
This archive was generated by hypermail 2.1.8 : Sun Dec 20 2009 - 23:15:18 EST


text:
Business intelligence like never before
Go from data to insights in minutes.
Any data, any way, anywhere. And all in one view.
Microsoft is recognized as a leader in the Gartner Magic Quadrant for Analytics and Business Intelligence Platforms–for 12 consecutive yearsDOWNLOAD REPORT
*This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Microsoft.
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
What is Power BI?
Power BI is a business analytics service that delivers insights to enable fast, informed decisions.
- Transform data into stunning visuals and share them with colleagues on any device.
- Visually explore and analyze data—on-premises and in the cloud—all in one view.
- Collaborate on and share customized dashboards and interactive reports.
- Scale across your organization with built-in governance and security.
Power BI for you
For analysts
Quickly go from data to insight to action. Connect to hundreds of sources, prep data with ease, and create beautiful reports, all in minutes.
For IT
Simplify management, achieve compliance, and keep data secure while giving people access to the insights they need.
For developers
Bring your apps to life with data. Easily embed interactive data visuals and deliver compelling reports—with high fidelity, on any device.
Organizations worldwide are using Power BI
With Power BI, we can very quickly connect to a wide range of data sources with very little effort and use this data to run Heathrow more smoothly than ever before.
Stuart Birrell, Chief Information Officer
Heathrow Airport delivers airport calm with the help of Power BI.
With Power BI, we were able to see where we were significantly behind the regional trend, focus on the problem, and create a solution.
Matt Craig, Regional Vice President–Eastern Region
Retail and consumer goods
Top supermarket chain gains insight and boosts profitability with Power BI.
Discover what the industry says about Power BI
For 12 years in a row, Microsoft has been recognized as a leader in the Gartner Magic Quadrant for Analytics and Business Intelligence Platforms.
Power BI wins Editors' Choice in the PCMag.com self-service BI tool review roundup for the second consecutive year.
Meet the Microsoft Power platform
Turn insights into action when you combine PowerApps, Power BI, and Microsoft Flow. One seamlessly connected platform that empowers everyone to innovate.
Power BI
Visualize data through interactive, real-time dashboards and analytics that generate actionable insights.
Build apps in hours—not months—that easily connect to data, use Excel-like expressions to add logic, and run on the web, iOS, and Android devices.
Microsoft Flow
Include powerful workflow automation directly in your app with a no-code approach that connects to hundreds of popular apps and services.

subset: commoncrawl


text:
SCons / IDEIntegration
The SCons wiki has moved to https://github.com/SCons/scons/wiki/IDEIntegration
Table of Contents
- The SCons wiki has moved to https://github.com/SCons/scons/wiki/IDEIntegration
- Integrating scons into IDEs
Integrating scons into IDEs
IDEs can often parse the output of build tools like scons which output the warnings and errors from the compiler etc as if the IDE had called the compiler itself. By using scons with your favourite IDE the best of both worlds can be obtained.
- The build process is developed in a cross platform, text based flexible form, instead of all the build settings being recorded in some form only editable through GUI.
- All of the great features of the IDE - Text editors with code completion, debugging etc, clicking on errors to see the line of code that caused them etc Below are instructions to get started using scons with some particular IDEs.
Visual Studio .NET 2003 / Visual Studio 2005 (Windows)
- Launch Visual Studio with the /useenv command line switch otherwise it won't be able to find scons.
- File->New Project General->Make File Project
- Save the project into the same directory as your SConstruct file.
- In the project settings, just add "scons" as the build command , and "scons -c" as the clean command and configuration is done.
- You should now be able to build using scons by using the build menu from visual studio. Note: VS2005 seems to need absolute paths to filenames for the click-on-errors integration to work. --björnen
- For debug build the command should be "scons debug=1"
- For Rebuild All: "scons -c & scons" ("scons -c & scons debug=1" for debug)
Alternatively, you can use the
MSVSProject() builder in your SConstruct file to generate a Visual Studio project file.
Xcode (Mac OS X)
- File->New Project, choose "External Build System"
- Save the project into the same directory as your SConstruct file.
- In Groups and Files -> Targets, double click the target that was automatically created.
- In the Build Tool field, put the full path to scons - like "/System/Library/Frameworks/Python.framework/Versions/2.3/bin/scons
- Set the Directory field to the directory that contains the SConstruct file.
- You should now be able to build using the Build command from Xcode
- Right click "Executables" and choose "Add new custom executable" and point it to the executable you are building and then you can debug using Xcode.
- Use Debug -> Breakpoints menu to add a symbolic breakpoint at main() - just type main where it says 'Double click for Symbol' - if you don't add this break point none of the breakpoints set in the editors will work, because gdb doesn't have the symbol information until you start debugging (Jim Ingham suggests turning off "Lazy Symbol Loading" in Debug Preferences.) See also the hint to get proper error parsing on MacOSX.
Alternatively, you can use scons-xcode to generate project files automatically.
SConsolidator is an Eclipse plug-in that provides tool integration for SCons in Eclipse for a convenient C/C++ development experience. Its main features are:
- Convertion of existing CDT managed build projects to SCons projects
- Import of existing SCons projects into Eclipse with wizard support
- Interactive mode to quickly build single source files speeding up round trip times
- A special view for a convenient build target management of all workspace projects
- Graph visualization of build dependencies with numerous layout algorithms and search and filter functionality that enables debugging of SCons scripts More information can be found at http://sconsolidator.com and its update site is available at http://www.sconsolidator.com/update.
There is also and older Eclipse Plug-in for SCons, though its documentation is scarce to nonexistent (see plugin).
Pros: It offers integrated support for building doxygen documentation and cppunit tests.
Cons: It imposes a build tree hierarchy which may work for smaller projects, but would be cumbersome for larger projects.
See SCons Setup and Custom Project at the KDevelop FAQ. Here's a quick copy of these two topics.
How can I set up a project with SCons?
SCons is a software construction tool. KDevelop (as of version 3.2.2) does not support SCons projects directly. However, it is possible to set up a project very simply using SCons by writing a "stub" Makefile and using the "Custom Makefiles" project type. An example of a simple stub Makefile is the following (note that lines after target names should be indented with tabs, not spaces):
- project_name:
- scons clean:
- scons --clean This will enable the Build Project and Clean Project actions to work.
How to create a simple project with just a Makefile (also known as Custom Project) ?
Create a Custom Project. There is no direct way to create a custom project (i.e. a project which does use its own makefiles). Use Project->Import Existing Project instead. Remember to set the appropriate Project Type, labeled by an additional (Custom Makefiles) in the dialog. Use Project Options Early. Whenever you start a new project do not forget to set the Project->Project Options... to your needs.
Emacs and XEmacs
First of all, you are going to want PythonMode if you don't have it already. If you are running on a system with a package manager, you might wish to look there first. On my Fedora system, the base XEmacs install was missing many useful accessories. I achieved a more complete installation with the command:
- sudo yum install xemacs-packages-base xemacs-packages-base-el xemacs-packages-extra xemacs-packages-extra-el xemacs-packages-extra-info For Emacs, it is suggested to add the following to your .emacs files, to enable Python mode for SConstruct and SConscript files.
(setq auto-mode-alist (cons '("SConstruct" . python-mode) auto-mode-alist)) (setq auto-mode-alist (cons '("SConscript" . python-mode) auto-mode-alist))
For XEmacs, a different reference suggests an alternate syntax added to your ~/.xemacs/init.el:
(add-to-list 'auto-mode-alist '("SConstruct" . python-mode)) (add-to-list 'auto-mode-alist '("SConscript" . python-mode))
If you wish to invoke a compilation via SCons from within Emacs/XEmacs, there are two ways to go about it. You can add a simple Makefile stub to your project directory with a rule to immediately delegate to SCons instead. The simplest example is just:
- main:
- scons Make certain the second line begins with a tab character. make and gmake have a hangup about that. This is also helpful for others to invoke your project build who aren't used to invoking SCons directly. Emacs/Xemacs will normally invoke make or gmake as the default compile command, and this simple Makefile will then transfer the build to SCons.
You can also change your Emacs/XEmacs default compile command by adding the following to your init file:
- (defvar compile-command "scons") This setting might affect other projects you compile normally with make or gmake, but if you compile everything via SCons, it eliminates the clutter and indirection of the Makefile stubs. If you use Makefile stubs, you might discover you need a separate Makefile stub in each project subdirectory where you compile code.
Compilation mode and error navigation
Compilation mode and its usage is documented as part of the GNU Emacs Manual.
If you employ a custom or unusual build tool as part of your build process, you might find your Emacs/XEmacs is unable to navigate the error text in the compilation buffer. To fix this, you can provide a custom regular expression for the variable compilation-error-regexp-alist.
This is a fairly advanced undertaking. The page (efaq)Compiler error messages can get you started. It suggests cribbing something similar to what you require from the Emacs source for compile.el, which contains many elaborations. On my Fedora system, this file is located at /usr/share/xemacs/xemacs-packages/lisp/xemacs-base/compile.el, but only after I manually installed the package sources (.el files) as described above. If you only find compile.elc, you have the package installed, but not the package sources.
Hi MaxEnt -- here's what I use, it's much simpler. You'll need a recent emacs (more recent than 21.1). It just processes the filenames to remove the build dirs.
;;; SCons builds into a 'build' subdir, but we want to find the errors ;;; in the regular source dir. So we remove build/XXX/YYY/{dbg,final}/ from the ;;; filenames. (defun process-error-filename (filename) (let ((case-fold-search t)) (setq f (replace-regexp-in-string "[Ss]?[Bb]uild[\\/].*\\(final\\|dbg\\)[^\\/]*[\\/]" "" filename)) (cond ((file-exists-p f) f) (t filename)))) (setq compilation-parse-errors-filename-function 'process-error-filename)
Qt Creator
Qt Creator is a free, cross-platform, lightweight IDE. Although designed to integrate with Qt, it can be used for any C++ project.
To use it with scons:
- File | New file or project | Other project | Import existing project. Click the Choose button.
- Enter a name for the project and navigate to the source directory.
- Verify that the File selection is as you want or fine-tune it. Click the Continue button.
- Optional: choose if you want to add the files to a version control system.
Click the Done button. Qt Creator will add four files to the top-level directory:
- $PROJECT_NAME.includes
- $PROJECT_NAME.config
- $PROJECT_NAME.creator The most important one is $PROJECT_NAME.files, which is just a list of all the files you want to show in the IDE. See http://doc.qt.nokia.com/qtcreator/creator-project-generic.html for details.
Now you have to add the SConstruct and SConscript files to the IDE. Either edit by hand the $PROJECT_NAME.files or, in the IDE project browser, right click on the top-level directory and select "Add existing files", and then select SConstruct from the list. Do the same for the SConscripts.
Last step: adding a build and a clean target.
On the left pane, click "Projects". Verify that the tab name is actually your project. Click on "Build Settings". The "build directory" field is a bit misleading with scons. Don't modify the default, it will use the source top-level directory. Same for the "Tool chain" pull-down menu, leave the default, it is not used by scons.
Under "Build Steps", remove the "Make" item by hovering on "Details" and clicking the X that appears.
Click "Add Build Step", select "Custom process step", tick the "Enable custom process step", under "Command" enter the full path to scons. Leave the other fields as they are. Eventually pass a -j2 in the "Commands arguments".
Under "Clean Steps", do the same thing as for "Add Build Step", only difference is that you will add "-c" to "Commands arguments".
You are all set! :-)
On the left pane, click on "Edit". You will find the previous view, with the project browser. Your scons project is ready to be be built.
Geany is a free, cross-platform, lightweight IDE.
To use it with scons:
Project -> New (store the project file anywhere)
Project -> Properties -> On the Project tab : set the base path of the project to where the SConstruct file is.
Open a source file in the file browser : geany appears to keep different build settings for different source types.
Project -> Properties -> On the build tab :
set the compile and build command for the source type to "scons -j <cpu count>"
set the working dir to "%p" (which is the base path of the project where the SConstruct file is).
Optional : set the source file independant build commands too, and scons -c for clean, all with %p as the working dir.