Dear all,
I have a table of data values (6509 in each dimension) which
represents
global point values at a resolution of 1.5-degrees... I want to
perform a
linear interpolation to change the resolution of this data to 5-
minutes.
This will require 18 new values to be created above, below and to both
sides
of each existing data value in the current table (except in instances
where
a value is not surrounded by four values, eg. at the edges of the
table,
where only values available should be used).
If anyone has any helpful tips, or could create some Fortran code to
achieve
this, then I'd be very grateful.
Many thanks
smurray444
Dear all,
I have a table of data values (6509 in each dimension) which
represents
global point values at a resolution of 1.5-degrees... I want to
perform a
linear interpolation to change the resolution of this data to 5-
minutes.
This will require 18 new values to be created above, below and to both
sides
of each existing data value in the current table (except in instances
where
a value is not surrounded by four values, eg. at the edges of the
table,
where only values available should be used).
If anyone has any helpful tips, or could create some Fortran code to
achieve
this, then I'd be very grateful.
Many thanks
smurray444
Dear all,
I have a table of data values (6509 in each dimension) which
represents
global point values at a resolution of 1.5-degrees... I want to
perform a
linear interpolation to change the resolution of this data to 5-
minutes.
This will require 18 new values to be created above, below and to both
sides
of each existing data value in the current table (except in instances
where
a value is not surrounded by four values, eg. at the edges of the
table,
where only values available should be used).
If anyone has any helpful tips, or could create some Fortran code to
achieve
this, then I'd be very grateful.
Many thanks
smurray444
Huh, I wonder how the original date and time were maintained given that
the E-S datastore was lost in August of 2024.
Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
Huh, I wonder how the original date and time were maintained given that
the E-S datastore was lost in August of 2024.
There is a Date: line in the header of USENET posts.
On 3/10/2026 1:31 AM, Thomas Koenig wrote:
Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
Huh, I wonder how the original date and time were maintained given that
the E-S datastore was lost in August of 2024.
There is a Date: line in the header of USENET posts.
But all of the original postings were lost on E-S before Aug 2024 ???
This posting is from April of 2007. That means somebody reloaded the
2007 posting on E-S.
Lynn
On 3/10/2026 1:31 AM, Thomas Koenig wrote:
Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
Huh, I wonder how the original date and time were maintained given that
the E-S datastore was lost in August of 2024.
There is a Date: line in the header of USENET posts.
But all of the original postings were lost on E-S before Aug 2024 ???
This posting is from April of 2007. That means somebody reloaded the
2007 posting on E-S.
Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
On 3/10/2026 1:31 AM, Thomas Koenig wrote:
Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
Huh, I wonder how the original date and time were maintained
given that the E-S datastore was lost in August of 2024.
There is a Date: line in the header of USENET posts.
But all of the original postings were lost on E-S before Aug 2024
???
This posting is from April of 2007. That means somebody reloaded
the 2007 posting on E-S.
That is how USENET works, it is a flood and fill algorithm.
Each article has its own unique ID. News servers offer each other
the IDs of articles; those that are already found in the database
are rejected, but the ones that are not found are loaded.
So, if a server loses its database, it will refill, assuming that
others servers connect to it. The only thing it will lose is the
internal numbring, that news clients usually operate on.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,104 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492389:49:31 |
| Calls: | 14,151 |
| Calls today: | 2 |
| Files: | 186,281 |
| D/L today: |
2,698 files (1,032M bytes) |
| Messages: | 2,501,210 |
| Posted today: | 1 |