News

CDO: Version 1.9.5 released

Added by Uwe Schulzweida 4 days ago

New features:
  • Changed type of date from 32 to 64-bit integer to support years > 214748
  • remapycon: optimized by changing cell search method
  • expr: added support for zon<STAT> functions
  • expr: added function sellevelrange() and sellevidxrange()
  • gridfile: added extension ":N" to select grid number N from data file
New operators:
  • dhour<stat> - Multi-day hourly statistics
Fixed bugs:
  • seldate: segmentation fault (bug introduce in 1.9.4) [Bug #8499]
  • select: wrong timestamp when combining select with selyear (bug introduce in 1.8.1) [Bug #8576]
  • gradsdes: bug fix for rotated lon/lat grids
  • silent option produces newlines [Bug #8538]
  • remapnn/remapdis: wrong result with regular 2D source grids if nlat > nlon [Bug #8498]

Blue-Action: Progress report, OA, publications, Zenodo records

Added by Chiara Bearzotti 17 days ago

Dear all,

  • We have updated the Guidelines for uploading the dissemination records (=presentations and posters) to Zenodo. Please pay attention: we had some missing records in this reporting because either the link to the grant agreement number or to the Blue-Action community were forgotten in Zenondo (We do not want this to happen!). Please check carefully the last page of these guidelines: https://code.mpimet.mpg.de/projects/bg10/wiki/Use_of_Zenodo
  • Open Access REMINDER: we have a contractual obligation to give open access to all publications within 6 months from the date of publication. Sometimes this obligation is colliding with the embargo imposed by the publisher. If you have doubts on what is allowed to be published/shared/by whom/where/how, please check these guidelines: https://code.mpimet.mpg.de/projects/bg10/wiki/Rules_for_open_access

All the best,
Chiara

Blue-Action: Instructions for Zenodo: upload to Blue-Action

Added by Chiara Bearzotti 3 months ago

Dear all,
Some of you have reported on problems in uploading documents in Zenodo Blue-Action community.

Please make sure you follow these steps:
1) Log into Zenodo: no login, no upload.
2) You need to go to the Upload community, https://www.zenodo.org/deposit/new?c=blue-actionh2020
3) Choose file, it must be in PDF, max 50 GB, try to avoid long titles with spaces in between.
4) Click on “Start upload”,
5) Under “Progress” it should show the % of the upload: if you have troubles here and it gives you error, please try to upload the file another time/another day, the system seem to be under stress at the moment… If you are experiencing technical problems, please do not send messages to me, but contact Zenodo directly: http://about.zenodo.org/contact/
6) When everything (all fields) are completed, click on "Publish".
7) As a curator, I will receive a message that a new record has been added to the Blue-Ac tion community and I will be asked to “approve” it. Thus it is not automatic that you see the record as soon as you upload it.

Thank you so much!
Kind regards,
Chiara

Blue-Action: Annual meeting 27-28-29 November 2018 in Almada (PT)

Added by Chiara Bearzotti 3 months ago

The Annual Meeting will take place on 27-28-29 November 2018 in Costa da Caparica, Almada (PT)
The event will start at 9 am on Tuesday 27 November 2018.
Wed 28 November will be a full day for the breakout sessions.
The event will close at 12 noon on Thursday 29 November 2018.

A draft agenda will be made available soon on the redmine WIKI https://code.mpimet.mpg.de/projects/bg10/wiki/Annual_Meeting_2019_27-29_November_2018_Almada_(PT)?parent=Annual_meetings

SAVE THE DATE!
Kind regards,
Chiara

Blue-Action: Deadlines for your inputs to the Progress Report

Added by Chiara Bearzotti 3 months ago

Dear partners,
this is a very important message related to our first Progress Report to the European Commission.
Read carefully the instructions below!
This reporting includes a progress (activity) and a financial report. The reporting period covers the period 1 Dec 2016-31 May 2018 (month 1 to month 18).

Activity report
This consists of a three component:
a) Description of the activities implemented at TASK level, full track of work done/objectives achieved/impacts achieved in terms of deliverables, milestones: Give evidence of what has been done, achieved, and long-term planning. Please do not repeat the content of the Deliverables/Milestones in the documents again, just refer to them, they will also be made available to the reviewers.
b) The full list of dissemination activities at WP level this means each WP should report on the progress achieved PER TASKS on the first 18 months with links to the Zenodo records where the presentations have been uploaded (Are they in Zenodo www.zenodo.org??? They have to! If not, please check out these guidelines: Wiki> Use of Zenodo)
c) Update of the data management plan at WP level. The document was drafted in month 3, this version need to updated now. This is to be updated.
Submission: WP leaders collect the information from the partners on implementation of tasks, dissemination activities of the PIs, data management and send the report to Coordination.
Internal deadline to deliver the draft to the coordination by 15 June 2018 to the Project Office (Chiara).
Template available in the redmine (WIKI>European Commission Review)

Financial report
A full financial report for each partner organization is due to the EC by 31 July 2018. The reporting period covers the period 1 Dec 2016-31 May 2018 (month 1 to month 18).
Submission by each partner organisation (financial officers) to Coordinator via the Participant Portal by this deadline.
Deadline for delivery to the EC is by 31 July 2018 at the latest!
Templates in the Participant Portal.

Please do not hesitate to ask questions if you are in doubt!
Kind regards,
Chiara

CDO: Version 1.9.4 released

Added by Uwe Schulzweida 3 months ago

New features:

  • Large data support: changed type of gridsize from 32 to 64-bit integer
  • remapbil, remapbic, remapnn, remapdis: optimized by changing point search method
  • Fldstat, Vertstat: added option weight=false to disable weighting

Fixed bugs:

  • option -r doesn't work [Bug #8334]
  • enspctl: changed parameter type from int to float [Bug #8386]
  • segfault with chained operators on timeseries data [Bug #8230]
  • setattribute: added support for \n in text attributes
  • expr: removed character [LlDd] from definition of float constants

Blue-Action: Your input for the "Arctic in situ observing systems" Survey

Added by Chiara Bearzotti 4 months ago

Dear Blue-Action colleagues,
We have been asked to circulate this request to all Blue-Action scientists by the project INTAROS.
This survey addresses Arctic in-situ observations of the ocean, atmosphere, terrestrial sphere and cryosphere, retrieved through established networks/observing systems as well as individual large projects.

Scope of the survey
To collect the information needed to assess the existing Arctic in-situ observing systems in terms of data delivery chain, accessibility, and spatial-temporal coverage.

Why is important?
The repository of the answers will enhance the visibility of the assessed data, and will facilitate data discovery for stakeholders and data users.

Link to the survey
Please reply to the survey here: [[https://intaros.nersc.no/node/651]]
Please read carefully the definitions, scope and contents on this page before starting the survey.

Official text
We are pleased to announce the public opening of the INTAROS questionnaire to survey the characteristics of the existing in-situ Arctic observing systems (questionnaire A). National and international institutions, agencies, and projects that have been (or are still) collecting in situ observations from fixed or mobile, permanent or temporary platforms in the Arctic are invited to answer to the questionnaire. The received answers will integrate those provided by the INTAROS partners, will be placed in an open access repository, and will be used to assess the Arctic observing system and analyze its gaps. The assessment is in line with the assessments of climate data record and of measurement series done under the FP7 CORE-CLIMAX project and the H2020 GAIA-CLIM project, respectively. The repository of the answers will enhance the visibility of the assessed data, and will facilitate data discovery for stakeholders and data users.

Questions?
In case of questions or comments, please contact: intaros-quest @ nersc.no

Please help us in spreading the word, the more replies to the survey, the better!

Redmine User Information: Maintenance and Renaming of svn.zmaw.de

Added by Alexander Bugl 4 months ago

What will happen:

  • upgrade of the Subversion server svn.zmaw.de
  • renaming of the Subversion server svn.zmaw.de to svn.mpimet.mpg.de

When?

  • Tuesday, April 10th, 8 am - 9:30 am

Who/What is affected:

  • Subversion on the server has been upgraded to v1.8
  • The machine has been renamed to svn.mpimet.mpg.de

What to do after the maintenance:

If you are still using SVN repositories, then you should prepare them for future use:
  • You might need to accept a new SSL server certificate after svn commands:
    $ svn update
    Updating '.':
    Error validating server certificate for 'https://svn.zmaw.de:443':
     - The certificate is not issued by a trusted authority. Use the
       fingerprint to validate the certificate manually!
    Certificate information:
     - Hostname: svn.mpimet.mpg.de
     - Valid: from Apr  6 12:26:43 2018 GMT until Jul  9 12:26:43 2020 GMT
     - Issuer: Max-Planck-Gesellschaft, Muenchen, Bayern, DE
     - Fingerprint: 87:7E:34:73:AC:47:C8:0A:CA:D1:48:27:90:B9:2F:DB:8F:31:29:2C
    
  • The repositories might need to be upgraded:
    $ svn upgrade
    
  • if you are still using SVN repositories, then these repositories might need to be relocated using svn relocate after the maintenance, e.g. for repository libmtime:
    $ svn relocate https://svn.mpimet.mpg.de/svn/libmtime
    

1 2 3 ... 13 (1-10/121)

Also available in: Atom