I would just like to add that the README for OpenMPI at github has this
text now:
--enable-heterogeneous
Enable support for running on heterogeneous clusters (e.g., machines
with different endian representations). Heterogeneous support is
disabled by default because it imposes a minor
We have just spent today hunting down a user bug report for Xyce (which
uses Trilinos, and its Zoltan library) that turn out to be exactly this
issue -- the user is seeing strange results from Xyce, and one of our
developers tracked it to exactly the issue that MPI_Send "to" the same
processor is
This issue is still present in Karmic. It means that any user of GIS
software in the Ubuntu repositories that depends on proj.4 will get
incorrect results when working between NAD27 and NAD83 datums. This is
a serious problem, and the fix is simple (I posted the commands for
building it
Public bug reported:
Binary package hint: proj
I am using Ubuntu 8.04 (Hardy). This bug report pertains to the
proj-4.6.0_1 package, which I no longer have installed due to this bug
(I've installed from source instead).
The cartographic projection library, proj, is advertised as now
containing
I should have remarked on the source package I'm referring to. It's
this one:
https://launchpad.net/ubuntu/+source/proj
--
Cartographic projection library (proj) built without datum conversion grid data
https://bugs.launchpad.net/bugs/368065
You received this bug notification because you are a
And further, I should note that the problem is not just for North
America. The proj-datumgrid file includes information for US, Canadian,
French and New Zealand that presumably also makes datum conversions for
those areas incorrect when the grids are missing.
--
Cartographic projection library
Since Marcel states the /sys/module/processor/parameters/max_cstate
doesn't exist in the alpha5 version of the kernel in Intrepid, the issue
is apparently not resolved,and the only way to get max_cstate set is to
set it at boot time with modprobe.d options, just as it was before.
Setting probe
This issue also impacts use of VMware on certain CPUs.
See, for example,
http://www.phocean.net/?p=10
http://ubuntuforums.org/showthread.php?t=769948
and
https://help.ubuntu.com/community/VMware/Workstation
I find that with Hardy this problem is much less severe than it was in
Edgy, Feisty and
