Tuesday, November 2, 2010

arbcombo -- Notice of Public Meeting for November 18, 2010

The Air Resources Board will conduct a public meeting to hear a
report on updates to emissions inventories for trucks, buses, and
off-road equipment prior to considering amendments to the truck
and bus regulation and the off-road regulation.

This informational item for the November meeting focuses only on
the emissions inventory activity and emissions data and methods
and not the proposed regulatory amendments, which are scheduled
for December. ARB staff will provide at the time of the meeting,
a brief written report summarizing the inventory updates.
Detailed information regarding the inventory changes is available
as technical appendices to the ISORs. The technical appendix for
the truck and bus inventory is available at:
http://www.arb.ca.gov/regact/2010/truckbus10/truckbusappd.pdf.
The technical appendix for the off-road inventory is available
at:
http://www.arb.ca.gov/regact/2010/offroadlsi10/offroadappg.pdf.


To provide your comments before the Board Meeting, please go to:


http://www.arb.ca.gov/lispub/comm/bcsubform.php?listname=on-offroad10&comm_period=A

As indicated above, detailed information regarding the truck and
bus and off-road inventory changes are available as appendices to
the respective ISORs for the Truck and Bus and Off-Road rules,
which will be heard on December 16 or 17, 2010.

You are receiving this single arbcombo email because you are a
subscriber to or have made a public comment to one or more of the
following lists: ag, altdiesel, board, diesel-retrofit, ej,
ej-prp, gmbond, hdghg, hdsoftware, inuseidling, loco,
ms-mailings, offroad, onrdiesel, ordiesel, portable, porttruck,
railyard, sbidling, schoolbus, swcv, truck-idling, tru, zeb.

======================================================================
You are subscribed to one of the lists aggregated to make this
particular ARB combination listserve broadcast. To UNSUBSCRIBE:
Please go to http://www.arb.ca.gov/listserv/listserv.php and enter
your email address and click on the button "Display Email Lists."
To unsubscribe, please click inside the appropriate box to uncheck it
and go to the bottom of the screen to submit your request. You will
receive an automatic email message confirming that you have
successfully unsubscribed. Also, please read our listserve disclaimer
at http://www.arb.ca.gov/listserv/disclaim.htm .

The energy challenge facing California is real. Every Californian
needs to take immediate action to reduce energy consumption. For
a list of simple ways you can reduce demand and cut your energy
costs, visit the Flex Your Power website at www.fypower.org .
======================================================================

Rewarding positions in healthcare

Start training now.





========================================================================================================================== The WSO2 Identity Server team is pleased to announce the release of version 3.0.0 of the Open Source WSO2 Identity Server (IS). IS 3.0.0 release is available for download at http://wso2.org/downloads/identity . This is based on revolutionary the WSO2 Carbon< http://wso2.org/projects/carbon >framework, Middleware a la carte'. All the major features have been developed as pluggable Carbon components. *New Features* SAML 2.0 based Single Sign-on support OAuth Support Support for bulk-user import Various bug fixes and enhancements including architectural improvements to Apache Axis2, Apache Rampart, Apache Sandesha2 , WSO2 Carbon and other projects. *Other Key Features* Entitlement Engine with XACML 2.0 support. Claim based Security Token Service with SAML 1.1/SAML 2.0. Information cards support for SAML 1.1/2.0. OpenID Provider. Extension points for SAML assertion handling. XMPP based multi-factor authentication. Improved User Management. Claim Management. User Profiles and Profile Management. XKMS. Separable front-end and back-end - a single front-end server can be used to administer several back-end servers. Information Cards provider supporting Managed Information Cards backed by user name / password and self-issued cards. Multi-factor authentication with Information Cards. ** *Issues fixed in this release* ** This release of WSO2 Identity Server comes with a number of bug fixes, both in the base framework and the Identity Server specific components. All the issues which have been fixed in Identity Server 3.0.0 are recorded at following locations: WSO2 Identity Server< https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10310 > WSO2 Carbon Platform< https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10309 > *Known Issues* ** WSO2 Identity Server< https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10312 > WSO2 Carbon Platform< https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10311 > ** *How to Run* 1. Extract the downloaded zip. 2. Go to the bin directory in the extracted folder. 3. Run the wso2server.sh or wso2server.bat as appropriate. 4. Point your browser to the URL https://localhost:9443/carbon 5. Use "admin", "admin" as the user name and password. 6. If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server *How you can contribute* Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : carb ... @wso2.org | Subscribe< carb ... @wso2.org ?subject=subscribe>| Mail Archive < http://wso2.org/mailarchive/carbon-dev/ > - User List : iden ... @wso2.org | Subscribe< iden ... @wso2.org ?subject=subscribe>| Mail Archive < http://wso2.org/mailarchive/identity-user/ > Reporting Issues WSO2 encourages you to report issues and your enhancement requests for the WSO2 Identity Server using the public JIRA< http://www.wso2.org/jira/browse/IDENTITY >. You can also watch how they are resolved, and comment on the progress.. Discussion Forums Alternatively, questions could be raised using the forums available. WSO2 Identity Server Forum < http://wso2.org/forum/308 > : Discussion forum for WSO2 Identity Server developers/users ** *Support * We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology. For more details and to take advantage of this unique opportunity please visit http://wso2.com/support/ For more information about WSO2 Identity Server, please see http://wso2.org/projects/identity or visit the WSO2 Oxygen Tank< http://wso2.org/library >developer portal for addition resources. Thank you for your interest in WSO2 Identity Server. -The WSO2 Identity Server team _______________________________________________ Identity -user mailing list Iden ... @wso2.org https://wso2.org/cgi-bin/mailman/listinfo/identity-user Hi! The Netfilter project presents another development release of the conntrack-tools. This release includes: * IPv6-icmp fix for state synchronization. * Support for TCP window tracking (it requires a Linux >= 2.6.35). * Improvements and fixes for the NAT filtering support for the command line tool `conntrack'. * Patrick McHardy's conntrack zone support (See iptables' CT target). Among many others outstanding bugfixes. Specifically I'd like to thank Mohit Mehta from Vyatta for their prolific bug reporting and QA testing. Please, see changelog attached for more details. Q: How stable are the conntrack-tools? A: The daemon that allows to synchronize states between firewalls has been tested in a cluster environment composed of two stateful firewalls running Debian 5.0 (Lenny) with a Linux kernel 2.6.32, keepalived 1.1.15, using conntrackd in FT-FW mode. The test consisted of downloading the Linux kernel source code in a tarball file via HTTP and randomly (in periods of 10 seconds) unplugging cablelinks to force the fail-over between the nodes. The results has shown no hangs/closure in any TCP connection. Q: What are the conntrack-tools? A: The conntrack-tools are: - The userspace daemon so-called conntrackd that covers the specific aspects of stateful Linux firewalls to enable high availability solutions. It can be used as statistics collector of the firewall use as well. The daemon is highly configurable and easily extensible. - The command line interface (CLI) conntrack that provides an interface to add, delete and update flow entries, list current active flows in plain text/XML, current IPv4 NAT'ed flows, reset counters, and flush the complete connection tracking table among many other. Q: Where can I download it from? A: http://www.netfilter.org/projects/conntrack-tools/downloads.html Q: Where can I get more information about them? A: http://conntrack-tools.netfilter.org Q: Where can I have a look at the user manual? A: http://conntrack-tools.netfilter.org/manual.html On behalf of the Netfilter Core Team, Pablo. Mohit Mehta (4): conntrackd: `-i -x' does not display internal cache in XML conntrackd: update error message for max netlink socket size reached conntrackd: enforce strict logic for NetlinkBufferSize[*] clauses conntrackd: replace cryptic `mfrm' by `malformed' in `-s' Pablo Neira Ayuso (34): conntrackd: fix UDP filtering in configuration file conntrackd: add support for TCP window scale factor synchronization conntrackd: cleanup port addition in the message building path conntrackd: fix `conntrackd -c' if external cache is disabled conntrack: option `-t' in on the same line as `-m' in manpage conntrackd: PollSecs goes in the General clause for statistics conntrackd: split __run() routine for poll and event-driven modes doc: description on how to block traffic with conntrack was incomplete conntrack: fix `-L --src-nat --dst-nat' conntrack: revert fix `-L --src-nat --dst-nat' conntrack: fix `conntrack -L --src-nat --dst-nat' (second try) conntrack: `-L --src-nat --dst-nat' filter using AND, not OR logic conntrackd: complete TCP window scale support conntrack: expand array that maps option-flags to option-names conntrack: put all the commands and options code together conntrack: fix port filter with `--src-nat' and `--dst-nat' conntrack: add `--any-nat' to filter any NATted flow conntrack: add testsuite for NAT filtering options conntrack: re-fix inconsistent display with `--src-nat' and `--dst-nat' conntrack: fix bogus NATted flows in filtering conntrack: fix `conntrack --src-nat 3.3.3.3' and similar conntrack: fix `conntrack --src-nat 1.1.1.1' if PAT applied conntrack: fix `conntrack --any-nat 1.1.1.1' filtering conntrack: --[src|dst|any]-nat requires IP:PORT as argument conntrack: fix `conntrack --[src|dst|any]-nat IP:PORT' if port mismatches conntrack: cleanup parsing of the NAT arguments conntrackd: fix ICMPv6 support conntrack: add zone support conntrackd: open event handler once cache has been populated conntrackd: setup event reliability after handler creation conntrackd: fix parsing of NAT sequence adjustment in synchronization messages conntrackd: warn on TCPWindowTracking option (it requires kernel >= 2.6.35) build: update libnetfilter_conntrack dependency (>= 0.0.102) build: bump version to 0.9.15

Important Information about Google Buzz Class Action Settlement

Google rarely contacts Gmail users via email, but we are making an
exception to let you know that we've reached a settlement in a lawsuit
regarding Google Buzz (http://buzz.google.com), a service we launched
within Gmail in February of this year.

Shortly after its launch, we heard from a number of people who were
concerned about privacy. In addition, we were sued by a group of Buzz users
and recently reached a settlement in this case.

The settlement acknowledges that we quickly changed the service to address
users' concerns. In addition, Google has committed $8.5 million to an
independent fund, most of which will support organizations promoting
privacy education and policy on the web. We will also do more to educate
people about privacy controls specific to Buzz. The more people know about
privacy online, the better their online experience will be.

Just to be clear, this is not a settlement in which people who use Gmail
can file to receive compensation. Everyone in the U.S. who uses Gmail is
included in the settlement, unless you personally decide to opt out before
December 6, 2010. The Court will consider final approval of the agreement
on January 31, 2011. This email is a summary of the settlement, and more
detailed information and instructions approved by the court, including
instructions about how to opt out, object, or comment, are available at
http://www.BuzzClassAction.com.

--------------------------------------------------------------------
This mandatory announcement was sent to all Gmail users in the United
States as part of a legal settlement and was authorized by the United
States District Court for the Northern District of California.

Google Inc. | 1600 Amphitheatre Parkway | Mountain View, CA 94043

Monday, November 1, 2010

Compare several companies

Find the right fit





==================================================================================================================== On Fri 14-08-09 16:41:05, Andrew Morton wrote: On Fri, 14 Aug 2009 14:26:10 +0200 Jan Kara < ja ... @suse.cz > wrote: During truncate we are sometimes forced to start a new transaction as the amount of blocks to be journaled is both quite large and hard to predict. So far we restarted a transaction while holding truncate_mutex and that violates lock ordering because truncate_mutex ranks below transaction start (and it can lead to a real deadlock with ext3_get_blocks() allocating new blocks from ext3_writepage()). Luckily, the problem is easy to fix: We just drop the truncate_mutex before restarting the transaction and acquire it afterwards. We are safe to do this as by the time ext3_truncate() is called, all the page cache for the truncated part of the file is dropped and so writepage() cannot come and allocate new blocks in the part of the file we are truncating. The rest of writers is stopped by us holding i_mutex. For ext2 we have the comment: /* * truncate_mutex is for serialising ext2_truncate() against * ext2_getblock(). It also protects the internals of the inode's * reservation data structures: ext2_reserve_window and * ext2_reserve_window_node. */ does truncate_mutex also protect ext3's reservation data? If so, is that impacted by this patch? That's a good question: ext3 seems to use truncate_mutex to guard reservation internals as well. Currently, truncate calls ext3_discard_reservation() in the end of truncate. That is slightly suboptimal when we can drop truncate_mutex during truncate as that can lead to allocation from reservation window which is not well placed wrt the new file end. Otherwise I don't think there's any issue since reservation is just an interval of blocks we'd like to allocate from so it's not bound to blocks allocated to the inode in any way. I'll move ext3_discard_reservation() to the beginning of the truncate to fix the above issue. Thanks for the comment. Attached is a new version of the patch. Honza -- Jan Kara < ja ... @suse.cz > SUSE Labs, CR From fad69f21486f4b2d78444acc321803bdb571e9d7 Mon Sep 17 00:00:00 2001 From: Jan Kara < ja ... @suse.cz > Date: Tue, 11 Aug 2009 19:06:10 +0200 Subject: [PATCH] ext3: Fix possible deadlock between ext3_truncate() and ext3_get_blocks() During truncate we are sometimes forced to start a new transaction as the amount of blocks to be journaled is both quite large and hard to predict. So far we restarted a transaction while holding truncate_mutex and that violates lock ordering because truncate_mutex ranks below transaction start (and it can lead to a real deadlock with ext3_get_blocks() allocating new blocks from ext3_writepage()). Luckily, the problem is easy to fix: We just drop the truncate_mutex before restarting the transaction and acquire it afterwards. We are safe to do this as by the time ext3_truncate() is called, all the page cache for the truncated part of the file is dropped and so writepage() cannot come and allocate new blocks in the part of the file we are truncating. The rest of writers is stopped by us holding i_mutex. We also move discarding of a reservation window to the beginning of truncate so that we don't use it when an allocation happens while we have dropped truncate_mutex during the truncate. Signed-off-by: Jan Kara < ja ... @suse.cz > --- fs/ext3/inode.c | 23 +++++++++++++++++------ 1 files changed, 17 insertions(+), 6 deletions(-) diff --git a/fs/ext3/inode.c b/fs/ext3/inode.c index b49908a..f591e58 100644 --- a/fs/ext3/inode.c +++ b/fs/ext3/inode.c @@ -172,10 +172,21 @@ static int try_to_extend_transaction(handle_t *handle, struct inode *inode) * so before we call here everything must be consistently dirtied against * this transaction. */ -static int ext3_journal_test_restart(handle_t *handle, struct inode *inode) +static int truncate_restart_transaction(handle_t *handle, struct inode *inode) { + int ret; + jbd_debug(2, "restarting handle %p\n", handle); - return ext3_journal_restart(handle, blocks_for_truncate(inode)); + /* + * Drop truncate_mutex to avoid deadlock with ext3_get_blocks_handle + * At this moment, get_block can be called only for blocks inside + * i_size since page cache has been already dropped and writes are + * blocked by i_mutex. So we can safely drop the truncate_mutex. + */ + mutex_unlock(&EXT3_I(inode)->truncate_mutex); + ret = ext3_journal_restart(handle, blocks_for_truncate(inode)); + mutex_lock(&EXT3_I(inode)->truncate_mutex); + return ret; } /* @@ -2072,7 +2083,7 @@ static void ext3_clear_blocks(handle_t *handle, struct inode *inode, ext3_journal_dirty_metadata(handle, bh); } ext3_mark_inode_dirty(handle, inode); - ext3_journal_test_restart(handle, inode); + truncate_restart_transaction(handle, inode); if (bh) { BUFFER_TRACE(bh, "retaking write access"); ext3_journal_get_write_access(handle, bh); @@ -2282,7 +2293,7 @@ static void ext3_free_branches(handle_t *handle, struct inode *inode, return; if (try_to_extend_transaction(handle, inode)) { ext3_mark_inode_dirty(handle, inode); - ext3_journal_test_restart(handle, inode); + truncate_restart_transaction(handle, inode); } ext3_free_blocks(handle, inode, nr, 1); @@ -2435,6 +2446,8 @@ void ext3_truncate(struct inode *inode) */ mutex_lock(&ei->truncate_mutex); + ext3_discard_reservation(inode); + if (n == 1) { /* direct blocks */ ext3_free_data(handle, inode, NULL, i_data+offsets[0], i_data + EXT3_NDIR_BLOCKS); @@ -2495,8 +2508,6 @@ do_indirects: ; } - ext3_discard_reservation(inode); - mutex_unlock(&ei->truncate_mutex); inode->i_mtime = inode->i_ctime = CURRENT_TIME_SEC; ext3_mark_inode_dirty(handle, inode); -- 1.6.0.2 Hi data( gasoline ) str( gasoline ) 'data.frame': 60 obs. of 2 variables: $ octane: num 85.3 85.2 88.5 83.4 87.9 ... $ NIR : AsIs [1:60, 1:401] -0.050193 -0.044227 -0.046867 -0.046705 -0.050859 ... ..- attr(*, "dimnames")=List of 2 .. ..$ : chr "1" "2" "3" "4" ... .. ..$ : chr "900 nm" "902 nm" "904 nm" "906 nm" ... str( gasoline $NIR) AsIs [1:60, 1:401] -0.050193 -0.044227 -0.046867 -0.046705 -0.050859 ... - attr(*, "dimnames")=List of 2 ..$ : chr [1:60] "1" "2" "3" "4" ... ..$ : chr [1:401] "900 nm" "902 nm" "904 nm" "906 nm" ... is.matrix( gasoline $NIR) [1] TRUE so the second element of gasoline data frame is a matrix ?AsIs df<-data.frame(x=1:5, I(matrix(rnorm(10), 5,2))) df x matrix.rnorm.10...5..2..1 matrix.rnorm.10...5..2..2 1 1 0.187703.... 0.213312.... 2 2 -0.66264.... -0.47941.... 3 3 -0.82334.... -0.04324.... 4 4 -0.37255.... 0.883027.... 5 5 -0.28700.... -1.03431.... str(df) 'data.frame': 5 obs. of 2 variables: $ x : int 1 2 3 4 5 $ matrix.rnorm.10...5..2.: AsIs [1:5, 1:2] 0.187703.... -0.66264.... -0.82334.... -0.37255.... -0.28700.... ... Regards Petr r-he ... @r-project.org napsal dne 23.10.2009 18:43:56: I have read that one ,I want to this method to be used to my data.but I donot know how to put my data into R. James W. MacDonald wrote: bbslover wrote: Steve Lianoglou-6 wrote: Hi, On Oct 22, 2009, at 2:35 PM, bbslover wrote: Usage data( gasoline ) Format A data frame with 60 observations on the following 2 variables. octane a numeric vector. The octane number. NIR a matrix with 401 columns. The NIR spectrum and I see the gasoline data to see below NIR.1686 nm NIR.1688 nm NIR.1690 nm NIR.1692 nm NIR.1694 nm NIR.1696 nm NIR.1698 nm NIR.1700 nm 1 1.242645 1.250789 1.246626 1.250985 1.264189 1.244678 1.245913 1.221135 2 1.189116 1.223242 1.253306 1.282889 1.215065 1.225211 1.227985 1.198851 3 1.198287 1.237383 1.260979 1.276677 1.218871 1.223132 1.230321 1.208742 4 1.201066 1.233299 1.262966 1.272709 1.211068 1.215044 1.232655 1.206696 5 1.259616 1.273713 1.296524 1.299507 1.226448 1.230718 1.232864 1.202926 6 1.24109 1.262138 1.288401 1.291118 1.229769 1.227615 1.22763 1.207576 7 1.245143 1.265648 1.274731 1.292441 1.218317 1.218147 1.222273 1.200446 8 1.222581 1.245782 1.26002 1.290305 1.221264 1.220265 1.227947 1.188174 9 1.234969 1.251559 1.272416 1.287405 1.211995 1.213263 1.215883 1.196102 look at this NIR.1686 nm NIR.1688 nm NIR.1690 nm NIR.1692 nm NIR. 1694 nm NIR.1696 nm NIR.1698 nm NIR.1700 nm how can I add letters NIR to my variable, because my 600 independents never have NIR as the prefix. however, it is needed to model the plsr. for example aa=plsr(y~NIR, data=data ,....), the prefix NIR is necessary, how can I do with it? I'm not really sue that I'm getting you, but if your problem is that the column names of your data.frame don't match the variable names you'd like to use in your formula, just change the colnames of your data.frame to match your formula. BTW - I have no idea where to get this gasoline data set, so I'm just imagining: eg. colnames( gasoline ) <- c('put', 'the', 'variable', 'names', 'that', 'you', 'want', 'here') -steve -- Steve Lianoglou Graduate Student: Computational Systems Biology | Memorial Sloan-Kettering Cancer Center | Weill Medical College of Cornell University Contact Info: http://cbio.mskcc.org/~lianos/contact ______________________________________________ R-h ... @r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. thanks for you. but the numbers of indenpendence are so many, it is not easy to identify them one by one, is there some better way? You don't need to identify anything. What you need to do is read the help page for the function you want to use, so you (at the very least) know how to use the function. library(pls) data( gasoline ) fit <- plsr(octane~NIR, data= gasoline , validation = "CV") summary(fit) Data: X dimension: 60 401 Y dimension: 60 1 Fit method: kernelpls Number of components considered: 53 VALIDATION: RMSEP Cross-validated using 10 random segments. (Intercept) 1 comps 2 comps 3 comps 4 comps 5 comps 6 comps CV 1.543 1.372 0.3827 0.2522 0.2347 0.2455 0.2281 adjCV 1.543 1.367 0.3740 0.2497 0.2360 0.2407 0.2243 7 comps 8 comps 9 comps 10 comps 11 comps 12 comps 13 comps CV 0.2311 0.2352 0.2455 0.2534 0.2737 0.2814 0.2832 adjCV 0.2257 0.2303 0.2395 0.2473 0.2646 0.2705 0.2726 14 comps 15 comps 16 comps 17 comps 18 comps 19 comps 20 comps CV 0.2913 0.2932 0.2985 0.3137 0.3289 0.3323 0.3391 adjCV 0.2808 0.2821 0.2863 0.3008 0.3141 0.3172 0.3228 21 comps 22 comps 23 comps 24 comps 25 comps 26 comps 27 comps CV 0.3476 0.3384 0.3316 0.3213 0.3155 0.3118 0.3062 adjCV 0.3307 0.3217 0.3154 0.3057 0.3002 0.2964 0.2908 28 comps 29 comps 30 comps 31 comps 32 comps 33 comps 34 comps CV 0.3033 0.3034 0.3074 0.3083 0.3094 0.3087 0.3105 adjCV 0.2881 0.2881 0.2917 0.2926 0.2936 0.2929 0.2946 35 comps 36 comps 37 comps 38 comps 39 comps 40 comps 41 comps CV 0.3108 0.3106 0.3105 0.3104 0.3104 0.3105 0.3105 adjCV 0.2949 0.2947 0.2946 0.2945 0.2945 0.2945 0.2946 42 comps 43 comps 44 comps 45 comps 46 comps 47 comps 48 comps CV 0.3105 0.3105 0.3105 0.3105 0.3105 0.3105 0.3105 adjCV 0.2946 0.2946 0.2946 0.2946 0.2946 0.2946 0.2946 49 comps 50 comps 51 comps 52 comps 53 comps CV 0.3105 0.3105 0.3105 0.3105 0.3105 adjCV 0.2946 0.2946 0.2946 0.2946 0.2946 TRAINING: % variance explained 1 comps 2 comps 3 comps 4 comps 5 comps 6 comps 7 comps 8 comps X 70.97 78.56 86.15 95.4 96.12 96.97 97.32 98.1 octane 31.90 94.66 97.71 98.0 98.68 98.93 99.06 99.1 9 comps 10 comps 11 comps 12 comps 13 comps 14 comps 15 comps X 98.32 98.71 98.84 99.00 99.21 99.46 99.52 octane 99.20 99.24 99.36 99.44 99.49 99.51 99.58 16 comps 17 comps 18 comps 19 comps 20 comps 21 comps 22 comps X 99.57 99.64 99.68 99.76 99.78 99.82 99.84 octane 99.65 99.69 99.78 99.81 99.86 99.89 99.92 23 comps 24 comps 25 comps 26 comps 27 comps 28 comps 29 comps X 99.88 99.91 99.92 99.93 99.94 99.95 99.96 octane 99.93 99.94 99.95 99.97 99.98 99.99 99.99 30 comps 31 comps 32 comps 33 comps 34 comps 35 comps 36 comps X 99.96 99.97 99.97 99.98 99.98 99.98 99.98 octane 99.99 100.00 100.00 100.00 100.00 100.00 100.00 37 comps 38 comps 39 comps 40 comps 41 comps 42 comps 43 comps X 99.99 99.99 99.99 99.99 100 100 100 octane 100.00 100.00 100.00 100.00 100 100 100 44 comps 45 comps 46 comps 47 comps 48 comps 49 comps 50 comps X 100 100 100 100 100 100 100 octane 100 100 100 100 100 100 100 51 comps 52 comps 53 comps X 100 100 100 octane 100 100 100 -- James W. MacDonald, M.S. Biostatistician Douglas Lab University of Michigan Department of Human Genetics 5912 Buhl 1241 E. Catherine St. Ann Arbor MI 48109-5618 734-615-7826 ______________________________________________ R-h ... @r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. -- View this message in context: http://www.nabble.com/data-frame-is-killing-me% 21-help-tp26015079p26029667.html Sent from the R help mailing list archive at Nabble.com. ______________________________________________ R-h ... @r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. ______________________________________________ R-h ... @r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.

Sunday, October 31, 2010

Solve crimes in your area

Get Started





====================================================================================================================== Things are moving forward for our first ever users conference, which will be held at the Le Meridien Parkhotel in Frankfurt on 14 March. I'm getting very excited about this, and it looks like we'll have at least 6 OGP members in attendance. The morning will consist of a short training course with a subset of our "A Day in the Life" training. This will cover a number of issues faced by systems and network administrators and how to use OpenNMS to solve them. The afternoon will consist of two tracks of one hour presentations on various aspects of OpenNMS, including using maps, syslog integration, reporting, using OpenNMS with Asterisk, etc. The cost will be 220€ with an early bird special of 199€ until 22 February. We've also reserved a block of rooms at the hotel which are first come, first serve. Registration information can be found here: http://www.nethinks.com/info/veranstaltungen/cal/event/20090314//list-75/tx_cal_phpicalendar//opennms_conference_europe_2009/ and as as always feel free to contact me with questions or comments. -T _______________________________________________________________________ Tarus Balog, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 503 961 7746 Email: tar ... @opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/wiki/index.php?page=MailingListFaq opennms-announce mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-announce

Saturday, October 30, 2010

Take care of your future

Inspire a generation





========================================================================================================================== [Geoff Whitten wrote] If there is no, or little, evidence linking Homo to African apes why do I have trouble picking Australopithecus from female Pan, and both of these from Homo habilis. Pongo, by contrast, is immediately and obviously different because of those big arched orbits [my reply] Not a cogent argument! Here is something of a counterexample: one might well have trouble picking a small, primitive marsupial from a rat. A kangaroo, by contrast, is immediately and obviously different! So, Pongo might have one or more striking autapomorphies which make it easily recognisable, and Homo more difficult to distinguish from Pan, yet Homo could be more closely related to Pongo. The resemblance between Homo and Pan could just be plesiomorphic. Stephen PS: This doesn't mean I support the "orangutan = Grehan theory"! :) ________________________________________ From: taxa ... @mailman.nhm.ku.edu [ taxa ... @mailman.nhm.ku.edu ] On Behalf Of John Grehan [ jgre ... @sciencebuff.org ] Sent: Friday, 4 September 2009 10:58 p.m. To: taxa ... @mailman.nhm.ku.edu Subject: Re: [Taxacom] molecular update There is no selection of characters other than restricting features to those that are either unique within the group being analyzed (species of large-bodied hominoids) or sufficiently rare in the outgroup (in this case all lesser apes and all Old World monkeys) to be considered derived for the in-group. If one relies on any morphological similarity to connect taxa then yes, one might get a different result due to the influence of primitive retentions. I don't know why Geoff has trouble picking Australopithecus from female Pan because he did not say why. I would have no trouble because the teeth are different (e.g. Australopithecus has thick enameled molars, posteriorly thickened palate, vertical, flattened zygoma with anteriorly oriented roots, not to mention the lack of a vertically raised supra-orbital torus across the glabella (between the eyes). The shape of the orbits of orangutans are not like those of gibbons in that the orangutan orbits are vertically oval. This is a unique feature among living taxa, and along with a narrow inter-orbital space, is shared with the fossil Sivapithecus. Interestingly, some australopiths also have vertically oval or ovoid orbits (chimps do not), including that hobbit fossil. Our studies have demonstrated that the cladistic morphological studies that seemed to back up the molecular data have many erroneous characters, especially for the chimpanzee relationship, and in one major study the genus Homo was not even included. For living taxa support for the chimpanzee relationship was limited to no more than 10 features, of which we could only corroborate two. In addition there has been agreement by one of the chimpanzee supporters on some of these errors (others no comment yet). But if one holds that the molecular evidence is necessarily the truth then none of these morphological issues matter since they are all, but default, independently uninformative. As independently uninformative (on phylogenetic relationships) morphology loses its predictive ability and therefore becomes phylogenetically meaningless, along with the entire fossil record. This is the elephant in the molecular room. John Grehan -----Original Message----- From: Geoff Witten [mailto: geof ... @rmit.edu.au ] Sent: Thursday, September 03, 2009 11:53 PM To: Stephen Thorpe; taxa ... @mailman.nhm.ku.edu ; John Grehan Subject: Re: [Taxacom] molecular update If there is no, or little, evidence linking Homo to African apes why do I have trouble picking Australopithecus from female Pan, and both of these from Homo habilis. Pongo, by contrast, is immediately and obviously different because of those big arched orbits. Like big gibbons. Perhaps they are even more closely related to each other (pongo and Hylobates) than to the African Hominidae, which in my mind should include Pan, Gorilla and Homo. Pongo and Homo are only close morphologically if you carefully select the morphological characters. Just thought someone should toss in the fact that there is abundant morphological evidence to back up the molecular if you select different morphological criteria. Geoff Geoff Witten Senior Lecturer in Anatomy Ph (03) 9925 7589 Fax 9467 8589 Stephen Thorpe < s.th ... @auckland.ac.nz > 4/09/09 12:31 >>> there is no evidence at all because morphology gives the 'wrong' answer No, no, no! That is not how evidence works - have you ever been on a jury (or in the dock!) Evidence that is 99% reliable can still give you the wrong answer (that is why it isn't 100% reliable!), but it is still 99% reliable evidence, not "no evidence at all" ... Stephen ________________________________________ From: taxa ... @mailman.nhm.ku.edu [ taxa ... @mailman.nhm.ku.edu ] On Behalf Of John Grehan [jgre ... @sciencebuff.org ] Sent: Friday, 4 September 2009 2:21 p.m. To: taxa ... @mailman.nhm.ku.edu Subject: Re: [Taxacom] molecular update Stephen, You have the argument correct. Your theorized response makes the point - that with the molecular theory there is no phylogenetic integration of the fossil and living taxa for human origins. And its not a matter of just 'no reliable evidence', there is no evidence at all because morphology gives the 'wrong' answer. John Grehan -----Original Message----- From: Stephen Thorpe [mailto: s.th ... @auckland.ac.nz ] Sent: Thursday, September 03, 2009 10:04 PM To: John Grehan; Taxacom Subject: RE: [Taxacom] molecular update John, If I understand you correctly, your argument is this: (1) Morphology supports a relationship between living humans and orangutans (probably in some people's cases more than others! :) (2) Molecular data contradict the human-orangutan relationship (3) The only evidence for relationships between living humans and fossil ancestors is morphological Therefore, if (2) wins over (1), then there is no reliable evidence for relationships between living humans and fossil ancestors Well, what are the possible responses? I think a " molecular person" could just stand firm and say that the evidence for establishing relationships involving fossil taxa is just not as good as for establishing relationships between extant taxa, so what? That was kind of obvious anyway, because fossils have fewer informative MORPHOLOGICAL characters than extant taxa ... Stephen ________________________________________ From: taxa ... @mailman.nhm.ku.edu [ taxa ... @mailman.nhm.ku.edu ] On Behalf Of John Grehan [jgre ... @sciencebuff.org ] Sent: Friday, 4 September 2009 1:45 p.m. To: Taxacom Subject: Re: [Taxacom] molecular update Here's something to think about that molecular systematists are going to have to figure out if they argue that the orangutan evidence is wrong because it conflicts with morphology. The morphological relationship with orangutans applies not only to humans, but also fossil hominids (australopiths). If this evidence is invalidated by the molecular theory then evolutionary theory is left with out any phylogenetic connection between the fossil and living representatives of the human lineage. If the orangutan similarities of humans and hominids is false then there is no empirical basis for accepting the reality of human similarities in fossil hominids either. So far the molecular theorists have sidestepped this problem. What a mess. John Grehan -----Original Message----- From: taxa ... @mailman.nhm.ku.edu [mailto: taxa ... @mailman.nhm.ku.edu ] On Behalf Of Jason Mate Sent: Thursday, September 03, 2009 3:28 PM To: Taxacom Subject: Re: [Taxacom] molecular update Maybe it will encourage one of the molecular supporters on this list to attempt to publish the knockout. If we were boxing Íd give it a go, alas it is by argumentation that we must feud and so I have to wait for more substantial emails to come. Maybe if you supplied the papers in question.... Jason _________________________________________________________________ Drag n' drop-Get easy photo sharing with Windows Live(tm) Photos. http://www.microsoft.com/windows/windowslive/products/photos.aspx _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here _______________________________________________ Taxacom Mailing List Taxa ... @mailman.nhm.ku.edu http://mailman.nhm.ku.edu/mailman/listinfo/taxacom The Taxacom archive going back to 1992 may be searched with either of these methods: (1) http://taxacom.markmail.org Or (2) a Google search specified as: site:mailman.nhm.ku.edu/pipermail/taxacom your search terms here

Friday, October 29, 2010

arbcombo -- Air Resources Board Public Hearing for Mandatory Reporting of Greenhouse Gas Emissions, December 16, 2010

The Air Resources Board will conduct a public hearing to consider
the Amendments to the Regulation for Mandatory Reporting of
Greenhouse Gas Emissions.

The Air Resources Board will conduct a public hearing to consider
the Amendments to the Regulation for Mandatory Reporting of
Greenhouse Gas Emissions.

This notice, the ISOR and all subsequent regulatory documents,
including the FSOR, when completed, are available on ARB's
website for this rulemaking at:

http://www.arb.ca.gov/regact/2010/ghg2010/ghg2010.htm

Inquiries concerning the substance of the proposed regulation may
be directed to the designated agency contact persons, Mr. Doug
Thompson, Manager of ARB Climate Change Reporting Section,
Planning and Technical Support Division at (916) 322-7062, or Mr.
Patrick Gaffney, Staff Air Pollution Specialist, at (916)
322-7303.


SUBMITTAL OF COMMENTS

Interested members of the public may also present comments orally
or in writing at the meeting, and comments may be submitted by
postal mail or by electronic submittal before the meeting. The
public comment period for this regulatory action will begin on
November 1, 2010. To be considered by the Board, written
comments, not physically submitted at the meeting, must be
submitted on or after November 1, 2010 and received no later than
12:00 noon on December 15, 2010, and must be addressed to the
following:

Postal mail: Clerk of the Board, Air Resources Board
1001 I Street, Sacramento, California 95814

Electronic submittal:
http://www.arb.ca.gov/lispub/comm/bclist.php


Thank you


You are receiving this single arbcombo email because you are a
subscriber to or have made a public comment to one or more of the
following lists: agriculture-sp, board, capandtrade, cc, cement,
chps, forestry, fuels, gas-trans, ghg-rep, ghgverifiers, ghg-ver,
glass, hydprod, landfills, manuremgmt, oil-gas, refineries, res,
sf6elec.

======================================================================
You are subscribed to one of the lists aggregated to make this
particular ARB combination listserve broadcast. To UNSUBSCRIBE:
Please go to http://www.arb.ca.gov/listserv/listserv.php and enter
your email address and click on the button "Display Email Lists."
To unsubscribe, please click inside the appropriate box to uncheck it
and go to the bottom of the screen to submit your request. You will
receive an automatic email message confirming that you have
successfully unsubscribed. Also, please read our listserve disclaimer
at http://www.arb.ca.gov/listserv/disclaim.htm .

The energy challenge facing California is real. Every Californian
needs to take immediate action to reduce energy consumption. For
a list of simple ways you can reduce demand and cut your energy
costs, visit the Flex Your Power website at www.fypower.org .
======================================================================