All the formulation for the prediction of water properties are published by International Association for the Properties of Water and Steam (IAPWS) so that they can be used.
It is often important to use exactly the same correlations so that that all the thermodynamic data are self-consistent. Therefore the formulations are standardized by an international body.
I do not think that the use of this formulae is in any way restricted because such restriction would defeat the very purpose - standarization.
See http://www.iapws.org/ for the collection of the current formulations.
There may be a restriction for a particular implementation (computer program) or sets of tables ( "lookup tables" and interpolation are often used for performance). Not sure.
Hope someone starts an extension to implement these kind of things in Gnumeric.
Cheers. Ephraim the horse.
Maintainability, maintainability, maintainability. Too little thought went into Linux maintainability so far.
In the long term, it is not the coolest environment which is going to prevail, but the one which is the most maintanable, because it can be incrementally improved.
I believe that the public at large underestimates the potential of nuclear as the environmentally-friendly source of energy. It is true that the current implementations of nuclear power plants are not satisfactory (environment wise), but then they have not been developed with environment in mind, the technology is young, and very little development occured over the last few decades (besides trying pushing lower prices for nuclear power plants of old designs).
Nuclear technology is complex, and this should be an argument for it, not against. It is complex; therefore, it can be optimized. It is potentially dangerous, but so is fire. One can learn to master it.
If only the politicians showed as much desire to developed clean nuclear energy as they spend on the bombs...
Well, 30 year-old system (only bug fixes) would be pretty secure. Reason: the paper appears to indicate that the half-life of bugs is ~3 years. A period of 10 half-lives is a established "benchmark" period to wait for an almost complete decay.
So either one debugs more, or waits longer (without constantly messing up with the software) to have things secure.
> Consider switching to ISO 8601 dates [YYYY-MM-DD] [demon.co.uk].
Your signature is right on. I wish more IT people had your sense and embraced standards where they exist. But instead they busy themselves with implementing any possible permutation to promote universal confusion. Cheers.
My life as a kde user (and maintener/upgrader of my own Linux desktop) would be greatly simplified if I could easily restore the crufty "desktop setting and application self-data" to default values, while preserving my important "user settings and data".
Examples of what I understand by crufty "desktop setting and application self data": fonts, menus, icons, colours, content of files.ICEauthority,.mcoprc,.i18n,.qt,.mailcap, temporary files, caches, symbolic links created by applications, and other things that are spread troughout my home directory which can make my desktop misbahave after upgrading from RedHat 8.something to Mandrake 9.something unless I delete them by hand.
Examples of what I understand "user data":.kppp connection info, imap mail server settings,.signature file, contact lists, email content, user documents, browser bookmarks, document history.
It all boils down to the mess that kde (oofice, gnome, and other applications) damp into my home directory and which makes my desktop computer choke after an upgrade. ooffice seems to be the worst damping brainless stuff into my home directory, but kde and gnome follow closely.
> DDS offers a valuable service; why the outrage at collecting fees for that service?
Well, a classification "service" for a system used in public libraries can be reasonably considered as part of basic infrastructure. As such, it should not be private because we (the people) expose ourself to a rip-off. One would expect that a publically-funded organization (a university?) does the maintanance work and does not charge the end user.
Slashdot Mirror
All the formulation for the prediction of water properties are published by International Association for the Properties of Water and Steam (IAPWS) so that they can be used. It is often important to use exactly the same correlations so that that all the thermodynamic data are self-consistent. Therefore the formulations are standardized by an international body. I do not think that the use of this formulae is in any way restricted because such restriction would defeat the very purpose - standarization. See http://www.iapws.org/ for the collection of the current formulations. There may be a restriction for a particular implementation (computer program) or sets of tables ( "lookup tables" and interpolation are often used for performance). Not sure. Hope someone starts an extension to implement these kind of things in Gnumeric. Cheers. Ephraim the horse.
OpenOffice lacks some features critical in my work area. The main one--sofisticated x-y graphing in Calc.
Maintainability, maintainability, maintainability. Too little thought went into Linux maintainability so far.
In the long term, it is not the coolest environment which is going to prevail, but the one which is the most maintanable, because it can be incrementally improved.
Nuclear technology is complex, and this should be an argument for it, not against. It is complex; therefore, it can be optimized. It is potentially dangerous, but so is fire. One can learn to master it.
If only the politicians showed as much desire to developed clean nuclear energy as they spend on the bombs ...
Disclaimer: I am a radiochemist.
And thanks to you, Jody (and a few others), gnumeric is, in my opinion, leading the pack of spreadsheets for Linux. Thanks!!
Well, 30 year-old system (only bug fixes) would be pretty secure. Reason: the paper appears to indicate that the half-life of bugs is ~3 years. A period of 10 half-lives is a established "benchmark" period to wait for an almost complete decay. So either one debugs more, or waits longer (without constantly messing up with the software) to have things secure.
Your signature is right on. I wish more IT people had your sense and embraced standards where they exist. But instead they busy themselves with implementing any possible permutation to promote universal confusion. Cheers.
Examples of what I understand by crufty "desktop setting and application self data": fonts, menus, icons, colours, content of files .ICEauthority, .mcoprc, .i18n, .qt, .mailcap, temporary files, caches, symbolic links created by applications, and other things that are spread troughout my home directory which can make my desktop misbahave after upgrading from RedHat 8.something to Mandrake 9.something unless I delete them by hand.
Examples of what I understand "user data": .kppp connection info, imap mail server settings, .signature file, contact lists, email content, user documents, browser bookmarks, document history.
It all boils down to the mess that kde (oofice, gnome, and other applications) damp into my home directory and which makes my desktop computer choke after an upgrade. ooffice seems to be the worst damping brainless stuff into my home directory, but kde and gnome follow closely.
Could I suggest two directories in user home:
.unimportant_settings_and_general_cruft_delete _if_desired
.user_important_setting_data_docs_dont_delete Best regards.
Well, a classification "service" for a system used in public libraries can be reasonably considered as part of basic infrastructure. As such, it should not be private because we (the people) expose ourself to a rip-off. One would expect that a publically-funded organization (a university?) does the maintanance work and does not charge the end user.