OK, I think there is a fair proposition about this question.
First, let's agree on some observations:
* The per-clock throughput of CPUs has been on an exponential increase curve, per last decades, ie. last 20-30 years matter a lot
* The proliferation of silicon compute devices has been on the increase for decades, ie last 10-20 years matter a lot (from the very small to the very big)
* The duty cycle of most silicon devices is not 100%; there are two notable exceptions: infrastructure (embedded) systems and supercomputers
* Despite regular interconnect technology upgrades, MPI has been the agreed standard for message passing since the early 90s
ref. http://www.top500.org/ ->Statistics for more details; so, here we talk about big machines, of high duty cycle, of using mostly a uniform API for synchronization.
Given Weather, Climate & Computational Fluid Dynamics codes (and some more), the temporal density of such calls is pretty good.
Concluding, MPI should be the most common *API* being called nowadays per unit of time;
there is still room for challenging this though: MPI Send/Recv calls have a few variants plus,
MPI stack implementors may have fragmented the codebase, to declare a clear winner...
But, why aim for the least, when you *can* do the most?
Environment-modules allow you to install multiple versions of software side-by-side, including multiple versions of Python.
Furthermore, it is next to trivial to install few 2.x and 3.x versions by using EasyBuild, see for examples at:
https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/p/Python
EasyBuild itself is written in Python and will run in any Python 2.x for x>=4.
Last but not least, EasyBuild may prove to be the more sane way to install Python packages in a cross-platform way;
anyone here having a better *cross-platform* offer?
by not replying, you do them a favor: you give them all the information they need to retry (noop => retry).
Try to put something like an answering machine, a hayes-modem with AT commands, Asterisk, whatever it takes to make sure you increase THEIR cost
(the cost maybe monetary if they have no fixed landline costs or, other like human time, when they are on flat-fee)
Likely, there will no shortage of such scams in the future, so you will get to re-use your equipment and effort.
Make sure you engage them otherwise, if everybody strays away from this, they have more chances to continue the scam.
btw. the Google Voice suggested by others is the right course/direction of action, if you have live business phone traffic coming in; otherwise, you risk your clients.
(and if it is such the case, $20 is a no-brainer to better serve your customers)
At 11$, it should fit the bill; made for scientists and engineers, should pass its own exams with 240 functions. The manual is here:
http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03519340-1.pdf
Why recommend it? I own it and it does the job, if the problem is really for a calculator:)
He could as well fine policemen, that stop for a piss while on duty.
They don't get a salary to piss after all, that's against the law or regulation or whatever!
Thinking about it, that's way more efficient for, and giving safety to, the taxpayer,
than collecting fines of people SMSing!
1. Get the high level view quickly
Ask for an inventory with parts-count list, including a network diagram, with services locations visible;
the complexity here is often to understand how the IP level (Layer 3) configuration relates to Layer 2 and Layer 1,
plus what interdependencies there are among services placed on systems (high availability features etc).
That kickstarts the technical handover, but you need the organizational one, too.
The Australians seem to get it right, carry on reading.
ps.
Here is my favorite hard-to-bend systems hand-over test: shutdown and restart everything. If you can:)
Yes, everything, yes: full shutdown, up to the electrical supply. You can't cheat that a lot; you'll miss info, but only secondary info. That will be good base for stellar (reverse) engineering.
Slashdot Mirror
First, let's agree on some observations:
ref. http://www.top500.org/ ->Statistics for more details; so, here we talk about big machines, of high duty cycle, of using mostly a uniform API for synchronization.
Given Weather, Climate & Computational Fluid Dynamics codes (and some more), the temporal density of such calls is pretty good.
Concluding, MPI should be the most common *API* being called nowadays per unit of time;
there is still room for challenging this though: MPI Send/Recv calls have a few variants plus,
MPI stack implementors may have fragmented the codebase, to declare a clear winner...
But, why aim for the least, when you *can* do the most? Environment-modules allow you to install multiple versions of software side-by-side, including multiple versions of Python. Furthermore, it is next to trivial to install few 2.x and 3.x versions by using EasyBuild, see for examples at: https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/p/Python EasyBuild itself is written in Python and will run in any Python 2.x for x>=4. Last but not least, EasyBuild may prove to be the more sane way to install Python packages in a cross-platform way; anyone here having a better *cross-platform* offer?
by not replying, you do them a favor: you give them all the information they need to retry (noop => retry).
Try to put something like an answering machine, a hayes-modem with AT commands, Asterisk, whatever it takes to make sure you increase THEIR cost (the cost maybe monetary if they have no fixed landline costs or, other like human time, when they are on flat-fee) Likely, there will no shortage of such scams in the future, so you will get to re-use your equipment and effort.
Make sure you engage them otherwise, if everybody strays away from this, they have more chances to continue the scam.
btw. the Google Voice suggested by others is the right course/direction of action, if you have live business phone traffic coming in; otherwise, you risk your clients. (and if it is such the case, $20 is a no-brainer to better serve your customers)
> http://en.wikipedia.org/wiki/University_of_Cyprus http://en.wikipedia.org/wiki/University_of_Cyprus != http://en.wikipedia.org/wiki/University_of_Nicosia
At 11$, it should fit the bill; made for scientists and engineers, should pass its own exams with 240 functions. The manual is here: http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c03519340-1.pdf Why recommend it? I own it and it does the job, if the problem is really for a calculator :)
...nice! how technology pace invents new commodities ;-)
He could as well fine policemen, that stop for a piss while on duty. They don't get a salary to piss after all, that's against the law or regulation or whatever! Thinking about it, that's way more efficient for, and giving safety to, the taxpayer, than collecting fines of people SMSing!
... some US fellows are about to learn Separation of Powers(and Duties) all over again...
Old married people, too much to lose? Depends how old!
Ask for an inventory with parts-count list, including a network diagram, with services locations visible; the complexity here is often to understand how the IP level (Layer 3) configuration relates to Layer 2 and Layer 1, plus what interdependencies there are among services placed on systems (high availability features etc).
That kickstarts the technical handover, but you need the organizational one, too. The Australians seem to get it right, carry on reading.
ps. :)
Yes, everything, yes: full shutdown, up to the electrical supply. You can't cheat that a lot; you'll miss info, but only secondary info. That will be good base for stellar (reverse) engineering.
Here is my favorite hard-to-bend systems hand-over test: shutdown and restart everything. If you can