Skip to content

Commit

Permalink
Update may_9_salamanca.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@linardian
linardian committed May 15, 2024
1 parent 0f9f25d commit f686bdc
Showing 1 changed file with 28 additions and 20 deletions.
48 changes: 28 additions & 20 deletions meetings/2024/may_9_salamanca.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Venue: Universidad Pontificia de Salamanca Calle Serranos 2, Salamanca

## Agenda

## Day 1 Thursday 9th May
### Day 1 Thursday 9th May
|TIME|TOPIC|PRESENTER
|----|-----|------|
|09:00 - 09:15|Welcome coffee|
Expand All @@ -31,7 +31,7 @@ Venue: Universidad Pontificia de Salamanca Calle Serranos 2, Salamanca

21:00 Social event (dinner)  

## Day 2 Thursday 10th May
### Day 2 Thursday 10th May
|TIME|TOPIC|PRESENTER
|----|-----|------|
|09:00 - 09:15|Welcome coffee|
Expand Down Expand Up @@ -71,7 +71,7 @@ Other attendees:

Fabio Palatta and Ida Migliaccio (Banca d'italia)
## Day 1 Thursday 9th May
## Introduction to new members
### Introduction to new members
New members have been introduced:
- Bryan Marquette (National Bank of Belgium) will participate in Work Stream 3
- Hadrien Kohl (Consultant) will participate in Work Stream 2
Expand All @@ -81,7 +81,7 @@ Some new collaborators have been also introduced:
- Arturo San Feliciano (Banco de Espana)
- Sergey Grebenshchikov (Bundesbank)

## Release of VTL version 2.1
### Release of VTL version 2.1
The User Manual and the Reference Manual will be frozen in the next days. The 2 documents in pdf version will be sent to the Secretariat via Written Procedure and will be published in the SDMX User Forum for final review.

The G4 file (grammar) will be update accordingly and will be available possibly by the end of June, in order to be ready to be published in the SDMX VTL official web page.
Expand All @@ -92,7 +92,7 @@ The final release of VTL 2.1 will be probably coordinated to the SDMX 3.1 versio
- Nicolas to coordinate the activity of producing the G4 file (grammar) possibily by end of June
- Angelo to produce the pdf of the two manuals and send to Secretariat via WP
- Angelo to post on SDMX the VTL 2.1 manuals for public review
## Current activities - WS1 - VTL docs (Attilio)
### Current activities - WS1 - VTL docs (Attilio)
**Requirements**
- Docs generation should be automated (CI/CD like) --> **YES**
- Single source for different outputs
Expand Down Expand Up @@ -122,7 +122,7 @@ The final release of VTL 2.1 will be probably coordinated to the SDMX 3.1 versio
- A good example of documentation is the pandora's one (https://pandas.pydata.org/docs/); at the moment it could be considerate a template for VTL home page


## Current activities - WS2 - VTL technical issues (Valentino)
### Current activities - WS2 - VTL technical issues (Valentino)
- Technical notes document drafted on github
- Some enhancements for error handling have been proposed:
- Define a standard coding
Expand All @@ -135,7 +135,7 @@ The final release of VTL 2.1 will be probably coordinated to the SDMX 3.1 versio
- WS2 to analyse proposed enhancements and produce a new version of the Technical Notes for the next VTL release
- Current pdf version will be generated and published together the 2 manuals in the official SDMX VTL site

## Current activities - WS3 - VTL language (Angelo)
### Current activities - WS3 - VTL language (Angelo)
- These are the main topics for the next release:
- User Defined Operators (UDO) (issue #51
- Viral attributes: complete revision
Expand All @@ -145,7 +145,7 @@ The final release of VTL 2.1 will be probably coordinated to the SDMX 3.1 versio
- Viral attributes revision to be prioritised
- Antonio to prepare a proposal for the join operator to be analysed and discussed

## Open issues about VTL: UDO and DL operators improvements
### Open issues about VTL: UDO and DL operators improvements
Angelo decribed more in detail current issues on User Defined Operators (UDO) and on Define Language (DL):
- Current issues with User Defined Operators
- #388: allow UDOs with several transformations (see procedures in VTL
Expand All @@ -162,35 +162,43 @@ Angelo decribed more in detail current issues on User Defined Operators (UDO) an
- Input will be coming from tools’ implementing teams (see Technical notes document) and from new requirements
- WS3 will take care of producing specificationsViral attributes revision to be prioritised

## Open issues about VTL: Dynamic web questionnaires
### Open issues about VTL: Dynamic web questionnaires

## Presentation of Meaningfuldata tools
### Presentation of Meaningfuldata tools
Antonio introduced Gustavo from Meaningfuldata who went through the VTL tools offered by the company.

Antonio presented a live demo of the VTL Suite and announced that in some weeks their VTL engine will be released as open source
## Day 2 Friday 10th May
## Key points for implementing VTL in production environment
### Key points for implementing VTL in production environment
Angelo gave a presentation about some key points on an enterprise calculation engine, based on the over 30 years' experience in Banca d'Italia:
- 0 implicit and 0 explicit cubes
- How to interpret missing values and nulls handling
- Calculability: Process cubesets, Status cubes and input vs output synchrony
- Process unit and parameters
- Historical processing and modularisation
## Implementing VTL in production environments: experiences from different organizations: Making Sense and HK consulting
### Implementing VTL in production environments: experiences from different organizations
#### Making Sense and HK consulting
Hadrien and Nicolas presented some issues about current version of VTL:
1. Some G4 issues that will be fixed in the next release of the grammar related to VTL version 2.1
1. Some G4 issues
2. Some operators containing constant values in their definition could be more efficient and flexible if variables are used
3. Language orthogonality: some operations can be expressed in multiple ways using different VTL operators: should this be avoided ?
4. Derived operators: some complex operators can be implemented by means of other core operators: ) be defined in VTL ?
4. Derived operators: some complex operators can be implemented by means of other core operators
5. Lacking of Technology Compatibility Kit (TCK)
6. Temporal types: too much is left to interpretation
7. Some useful operators can be introduced:
- getObs(ds, 1 order by id_1) -- returns the first ds line as key/value object (new type)
- scalar := getScalar(observation, "Me_2") -- returns the Me_2 scalar value

NBB/Meaningfuldata|Antonio/Bryan
||ECB (testing activities with VTL)|Noah
|11:30 - 11:45|Coffee break|
|11:45 - 12:30|Current collaboration activities
## AOB

**Actions**
- Point 1: all the errors found will be fixed in the next release of the grammar related to VTL version 2.1
- Points 3 and 4: The current approach, as Edgardo pointed out, has been adopted after a similar discussion during the preparation of VTL version 1.1. Since VTL is not a programming language and it is more user-oriented, it is preferable to keep it more user-friendly and less error-prone, even if has some redundancies
- Point 5: The currently on-going activity of VTL docs (WS1) is aimed at building a first "implicit" version of a TCK; possible ehancements can be discussed at the end of this task
- The other points will be analysed and discussed in ad-hoc WS2 and WS3 meetings

#### NBB/Meaningfuldata
- Bryan briefly described NBB's current activities on VTL; at the moment final users do not have direct "hands on" the language and there is an "expert group" that implements business requirements using VTL Suite by Meaningfuldata
- In the next months more statistical flow will be added to the current solution and once the expert group has reached a good knowledge of VTL, training programs will be set up involving all the final business users
#### ECB testing activities with VTL
### Current collaboration activities
### AOB
Next VTL physical meeting will be held ...

0 comments on commit f686bdc

Please sign in to comment.