193,161 research outputs found
OPENDAP/bes: BES version 3.21.0 for Hyrax-1.17.0
No full text<p>News for 3.21.0</p>
<p>We reworked the way we implement the BES's singletons (or more of them at least)
so that they use the Meyers Singleton pattern. This includes the EffectiveUrlCache
and TheBESKeys classes.</p>
<p>We have made significant advances to supporting HDF5 files in the DMR++ builder
and interpreter. Our support is close to complete with only a very few features
not supported. This support now includes HDF5's Varying-length string arrays. The
software now also supports scalar strings in all their forms. Note that we also
added support for fixed length string arrays in the DMR++ builder and interpreter.</p>
<p>This version of the BES includes a new feature, dependent on the newest version
of libdap, that reduces the time needed to build NetCDF4 responses by a factor
of 10 or more when the variables in the response are not spatially subset (that
is, when all variables in the response are returned in their entirety). It is still
possible to subset at the variable level and get this performance boost. This is
the 'Direct I/O' feature added ti libdap. NOTE: To use this feature, you must
rebuild DMR++ files using the version of the DMR++ builder associated with this
version of the BES (or get_dmrpp tool from the hyrax-1.16.8-356 build).</p>
<p>We improved the performance of finding the effective URL for a data item when it
is accessed via a series of redirect operations, the last of which is a signed
AWS URL. This is a common case for data stored in S3.</p>
<p>We have added generic Memory and File caching, tailored specifically toward the
cases that arise when serving data from S3 using the DMR++ system.</p>
<p>The BES now has much better support for response size and time limits. Users are
warned about responses that are too large <em>before</em> they are built and the BES
now exits gracefully when a response takes too long to build. The limits are
configurable.</p>
<p>We replaced a home-grown HTTP connection pool with a scheme provided by libcurl.
The two have equivalent performance, but the libcurl version is much easier to
maintain and might offer room for improvement in the future.</p>
<p>C99 compatibility improvements for the GCTP code in/used-by the HDF5 handler.
Thanks ti Florian Weimer <fweimer at redhat.com> for those fixes.</p>
<p>We have added a BES module that can work with S3 using the DMR++ system. This
provides a data flow that is similar to the one we provide for Hyrax in the Cloud
as developer for NASA, but this new module does not make use of the NASA/ESDIS
CMR system to resolve 'NASA Granules' to URLs. This will enable other groups to
use the DMR++ system to serve data from S3.</p>
<p>We have adopted C++-14 as aggressively as we can, resulting in fewer lines of code,
better memory management and more efficient code.</p>
<p>We have moved more of the handlers to build/use DAP4 as the default response format
and build DAP2 responses from those. This reduces the amount of code we have to
maintain.</p>
<p>The BES can sign S3 URLs using the AWS V4 signing scheme. This uses the Credentials
Manager system.</p>
<p>The bundled grid() and geogrid() server side functions now support DAP4.</p>
OPENDAP/bes: BES version 3.21.0 for Hyrax-1.17.0
No full text<p>News for 3.21.0</p>
<p>Reworked the way we implement the BES's singletons (or more of them at least)
so that they use the Meyers Singleton pattern. This includes the EffectiveUrlCache
and TheBESKeys classes.</p>
<p>We have made significant advances to supporting HDF5 files in the DMR++ builder
and interpreter. Our support is close to complete with only a very few features
not supported. This support now includes HDF5's Varying-length string arrays. The
software now also supports scalar strings in all their forms. Note that we also
added support for fixed length string arrays in the DMR++ builder and interpreter.</p>
<p>This version of the BES includes a new feature, dependent on the newest version
of libdap, that reduces the time needed to build NetCDF4 responses by a factor
of 10 or more when the variables in the response are not spatially subset (that
is, when all variables in the response are returned in their entirety). It is still
possible to subset at the variable level and get this performance boost. This is
the 'Direct I/O' feature added ti libdap. NOTE: To use this feature, you must
rebuild DMR++ files using the version of the DMR++ builder associated with this
version of the BES (or get_dmrpp tool from the hyrax-1.16.8-356 build).</p>
<p>We improved the performance of finding the effective URL for a data item when it
is accessed via a series of redirect operations, the last of which is a signed
AWS URL. This is a common case for data stored in S3.</p>
<p>We have added generic Memory and File caching, tailored specifically toward the
cases that arise when serving data from S3 using the DMR++ system.</p>
<p>The BES now has much better support for response size and time limits. Users are
warned about responses that are too large <em>before</em> they are built and the BES
now exits gracefully when a response takes too long to build. The limits are
configurable.</p>
<p>We replaced a home-grown HTTP connection pool with a scheme provided by libcurl.
The two have equivalent performance, but the libcurl version is much easier to
maintain and might offer room for improvement in the future.</p>
<p>C99 compatibility improvements for the GCTP code in/used-by the HDF5 handler.
Thanks ti Florian Weimer <fweimer at redhat.com> for those fixes.</p>
<p>We have added a BES module that can work with S3 using the DMR++ system. This
provides a data flow that is similar to the one we provide for Hyrax in the Cloud
as developer for NASA, but this new module does not make use of the NASA/ESDIS
CMR system to resolve 'NASA Granules' to URLs. This will enable other groups to
use the DMR++ system to serve data from S3.</p>
<p>We have adopted C++-14 as aggressively as we can, resulting in fewer lines of code,
better memory management and more efficient code.</p>
<p>We have moved more of the handlers to build/use DAP4 as the default response format
and build DAP2 responses from those. This reduces the amount of code we have to
maintain.</p>
<p>The BES can sign S3 URLs using the AWS V4 signing scheme. This uses the Credentials
Manager system.</p>
<p>The bundled grid() and geogrid() server side functions now support DAP4.</p>
OPENDAP/bes: BES-3.21.0-46 for Hyrax-1.17.0
No full text<p>News for 3.21.0-46</p>
<p>Reworked the way we implement the BES's singletons (or more of them at least)
so that they use the Meyers Singleton pattern. This includes the EffectiveUrlCache
and TheBESKeys classes.</p>
<p>We have made significant advances to supporting HDF5 files in the DMR++ builder
and interpreter. Our support is close to complete with only a very few features
not supported. This support now includes HDF5's Varying-length string arrays. The
software now also supports scalar strings in all their forms. Note that we also
added support for fixed length string arrays in the DMR++ builder and interpreter.</p>
<p>This version of the BES includes a new feature, dependent on the newest version
of libdap, that reduces the time needed to build NetCDF4 responses by a factor
of 10 or more when the variables in the response are not spatially subset (that
is, when all variables in the response are returned in their entirety). It is still
possible to subset at the variable level and get this performance boost. This is
the 'Direct I/O' feature added ti libdap. NOTE: To use this feature, you must
rebuild DMR++ files using the version of the DMR++ builder associated with this
version of the BES (or get_dmrpp tool from the hyrax-1.16.8-356 build).</p>
<p>We improved the performance of finding the effective URL for a data item when it
is accessed via a series of redirect operations, the last of which is a signed
AWS URL. This is a common case for data stored in S3.</p>
<p>We have added generic Memory and File caching, tailored specifically toward the
cases that arise when serving data from S3 using the DMR++ system.</p>
<p>The BES now has much better support for response size and time limits. Users are
warned about responses that are too large before they are built and the BES
now exits gracefully when a response takes too long to build. The limits are
configurable.</p>
<p>We replaced a home-grown HTTP connection pool with a scheme provided by libcurl.
The two have equivalent performance, but the libcurl version is much easier to
maintain and might offer room for improvement in the future.</p>
<p>C99 compatibility improvements for the GCTP code in/used-by the HDF5 handler.
Thanks ti Florian Weimer for those fixes.</p>
<p>We have added a BES module that can work with S3 using the DMR++ system. This
provides a data flow that is similar to the one we provide for Hyrax in the Cloud
as developer for NASA, but this new module does not make use of the NASA/ESDIS
CMR system to resolve 'NASA Granules' to URLs. This will enable other groups to
use the DMR++ system to serve data from S3.</p>
<p>We have adopted C++-14 as aggressively as we can, resulting in fewer lines of code,
better memory management and more efficient code.</p>
<p>We have moved more of the handlers to build/use DAP4 as the default response format
and build DAP2 responses from those. This reduces the amount of code we have to
maintain.</p>
<p>The BES can sign S3 URLs using the AWS V4 signing scheme. This uses the Credentials
Manager system.</p>
<p>The bundled grid() and geogrid() server side functions now support DAP4.</p>
Correlation between the variation of BE (Delta BES) and %EWL.
No full textA Correlation coefficient between %EWL and Delta BES and the distribution of the entire sample. rs = -0.186 p = 0.033B Correlation coefficient and distribution of patients who had a negative Delta BES. rs = -0.101 p = 0.306C Correlation coefficient and distribution of patients who had a positive Delta BES. rs = -0.378 p = 0.122
%EWL, % of excess weight loss; Delta BES, BES at one year—preoperative BES; rs, correlation coefficient. A Correlation coefficient between %EWL and Delta BES and the distribution of the entire sample. rs = -0.186 p = 0.033 B Correlation coefficient and distribution of patients who had a negative Delta BES. rs = -0.101 p = 0.306 C Correlation coefficient and distribution of patients who had a positive Delta BES. rs = -0.378 p = 0.122</p
Author-wise bibliometric analysis based on entropy.
No full textAuthor-wise bibliometric analysis based on entropy.</p
Ontogenetic reduction in thermal tolerance is not alleviated by earlier developmental acclimation in Rana temporaria
No full textThis research was supported by MINECO (CGL2012-40246) and MEC (CGL2017-86924-P) Grants. U.E.U. was supported by a Ph.D. award (BES-2013-063203) from ME
Going Beyond Counting First Authors in Author Co-citation Analysis
No full textThe present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
Establishment of EH-BES cell line in 2i medium.
No full text<p>(A) Embryos from BALB/C<sup>Cat/Cat</sup> mice were separately seeded in 2i medium on gelatin-coated plastics and ES cells-like colony emerged in 3 days. (B) EH-BES cell line was established and maintained with or without feeders. (C) EH-BES cells were AP-staining positive (left); EH-BES cells showed Nanog-expression by immunostaining analysis (right). (D) EH-BES cells showed Oct4-expression. (E) EH-BES cells showed Sox2-expression. DAPI stain indicates nuclei in blue. Scale bars stand for 100 µm.</p
- …
