ECMT

Tuesday, October 13 2020

Friday, October 9 2020

Friday, September 25 2020

Friday, September 11 2020

Staging

Version number on the login screen

Results per page

Renaming "Diesel only" field to "No catenary"

Bulk editing notice, if an object is selected where the editing cannot be performed on

Long dwell time on a station (midnight crossing)

Show running days instead of validity period in TCR tooltip

Select objects on this page or on all pages

Extend traffic measures matrix of TCRs with commuter trains

Presentation of objects on overlapping lines

Multiple day object presentation

Personal filters

Detection of overlapping objects

Demo

In line with the staging.

Description

Please find here the summary of the ECMT developments, including the latest news from the Sprint Review meetings and also the candidate of features available currently in the Staging or in the Demo site.

ECMT Production                                                                           

https://ecmt-online.rne.eu/

ECMT Staging

https://ecmt.staging.i0.hu/

Both environments are accessible without a user account, using the public access as an anonymous profile.

Documentation

The documentation is publicly available on the following page: https://ecmt-online.rne.eu/documentation

Recent Activity

Filter 

January 15, 2021

  • 10:39am
    [ECMT] [Discussions] Máté Bak created 2021.01.15. Sprint review Friday, January 15Máté Bak created 2021.01.15. Sprint review  ReviewKey enter should start a search (bug)Enter button has reset the form on the search page and on the object pageRemove day from the calendar (bug)The user was not able to remove properly the days from the daily calendar view. It always removed the neighbouring days or something like that. It blinks now upon selection, which is an attribute of this plugin.Detecting overlapping objects (optimization)We've added a pre-loader to the page. First, we show the empty grid and in the meantime, we are permanently searching for the detected overlapping. The pre-loader shows the % of the progress also which conflicts are searched.Catalogue conflict overtaking needs the most time, we are still working on the optimization of that.If there is an update on a catalogue, then due to the caching of the objects to the timetable (conflict detection) table, it might take time (5 minutes) when the update is visible on the conflict.Idea: maybe we can show already the detected results on the grid, while we are still searching for other types of conflicts.When the URL of the form is fixed and the pages of the results are added, it will be ready to roll-out to staging.WHAT/Next sprintOpen object automatically in new tabWhen the user saves preparation mode (from published) edit view should openChart loading upon user trigger*rne.eu certificationUnremovable day (bug)Máté Bak created 2021.01.15. Sprint review

    [ECMT] [Discussions] Máté Bak created 2021.01.15. Sprint review

    Friday, January 15

    Máté Bak created 2021.01.15. Sprint review

     

    Review

    Key enter should start a search (bug)

    Enter button has reset the form on the search page and on the object page

    Remove day from the calendar (bug)

    The user was not able to remove properly the days from the daily calendar view. It always removed the neighbouring days or something like that. It blinks now upon selection, which is an attribute of this plugin.

    Detecting overlapping objects (optimization)

    We've added a pre-loader to the page. First, we show the empty grid and in the meantime, we are permanently searching for the detected overlapping. The pre-loader shows the % of the progress also which conflicts are searched.
    Catalogue conflict overtaking needs the most time, we are still working on the optimization of that.
    If there is an update on a catalogue, then due to the caching of the objects to the timetable (conflict detection) table, it might take time (5 minutes) when the update is visible on the conflict.

    Idea: maybe we can show already the detected results on the grid, while we are still searching for other types of conflicts.

    When the URL of the form is fixed and the pages of the results are added, it will be ready to roll-out to staging.

    WHAT/Next sprint

    Open object automatically in new tab

    When the user saves preparation mode (from published) edit view should open

    Chart loading upon user trigger

    *rne.eu certification

    Unremovable day (bug)

    Review

    Key enter should start a search (bug)

    Enter button has reset the form on the search page and on the object page

    Remove day from the calendar (bug)

    The user was not able to remove properly the days from the daily calendar view. It always removed the neighbouring days or something like that. It blinks now upon selection, which is an attribute of this plugin.

    Detecting overlapping objects (optimization)

    We've added a pre-loader to the page. First, we show the empty grid and in the meantime, we are permanently searching for the detected overlapping. The pre-loader shows the % of the progress also which conflicts are searched.
    Catalogue conflict overtaking needs the most time, we are still working on the optimization of that.
    If there is an update on a catalogue, then due to the caching of the objects to the timetable (conflict detection) table, it might take time (5 minutes) when the update is visible on the conflict.

    Idea: maybe we can show already the detected results on the grid, while we are still searching for other types of conflicts.

    When the URL of the form is fixed and the pages of the results are added, it...

    Read more

December 4, 2020

  • 10:53am
    [ECMT] [Discussions] Máté Bak created 2020.12.04. Sprint review Friday, December 4Máté Bak created 2020.12.04. Sprint review   ReviewCriss-crossing objects with offsetIt's a general solution now, not specifically for the use case when the objects and their lines meet only once or twice.Scenario table dataIf only one day was selected for a continuous TCR (valid from-to the same) and the all days option was used, it shows properly on the chart, but when the user opens the object from the chart, ECMT shows a huge error message on the object page. It was fixed and no error message is shown.Drupal core updateDelete/remove locationThere is a problem when we delete a location from the system. In this case, we show a message in the timetables that there is a "missing location". Editing of such an object leads to error.We discussed that in the future, we should cover the use case when a location becomes invalid (unpublished), but real deletion should never happen. Then, unpublished location cannot be added to a line. We will work on the requirements now, and implementation will come in 2021.Disabled save option for path editingSave button was available but didn't work for any object if the transparency is set by the user with the slider. The tool added 2 digits to the decimal number, instead of the expected 3 digits.WHAT/Next sprintPreloader animation for the chartTo show a loading page feature, while the user has to wait for the chart. It will be useful for crowded charts, where thousands of objects must be loaded.Optimization of big conflict pagesCurrently, the conflict detection leads to performant issues. We will try to improve this, but most likely the release of this feature will be in 2021.Optimization of release timeIncluding the conflict detection feature, the release time is too long and we have found a solution to narrow it down.ReleasesStaging test on Monday morning for this couple new fixes. If we don't find any blocking point, then production release on Monday afternoon.Máté Bak created 2020.12.04. Sprint review

    [ECMT] [Discussions] Máté Bak created 2020.12.04. Sprint review

    Friday, December 4

    Máté Bak created 2020.12.04. Sprint review

     

     

    Review

    Criss-crossing objects with offset

    It's a general solution now, not specifically for the use case when the objects and their lines meet only once or twice.

    Scenario table data

    If only one day was selected for a continuous TCR (valid from-to the same) and the all days option was used, it shows properly on the chart, but when the user opens the object from the chart, ECMT shows a huge error message on the object page. It was fixed and no error message is shown.

    Drupal core update

    Delete/remove location

    There is a problem when we delete a location from the system. In this case, we show a message in the timetables that there is a "missing location". Editing of such an object leads to error.

    We discussed that in the future, we should cover the use case when a location becomes invalid (unpublished), but real deletion should never happen. Then, unpublished location cannot be added to a line. We will work on the requirements now, and implementation will come in 2021.

    Disabled save option for path editing

    Save button was available but didn't work for any object if the transparency is set by the user with the slider. The tool added 2 digits to the decimal number, instead of the expected 3 digits.

    WHAT/Next sprint

    Preloader animation for the chart

    To show a loading page feature, while the user has to wait for the chart. It will be useful for crowded charts, where thousands of objects must be loaded.

    Optimization of big conflict pages

    Currently, the conflict detection leads to performant issues. We will try to improve this, but most likely the release of this feature will be in 2021.

    Optimization of release time

    Including the conflict detection feature, the release time is too long and we have found a solution to narrow it down.

    Releases

    Staging test on Monday morning for this couple new fixes. If we don't find any blocking point, then production release on Monday afternoon.

     

    Review

    Criss-crossing objects with offset

    It's a general solution now, not specifically for the use case when the objects and their lines meet only once or twice.

    Scenario table data

    If only one day was selected for a continuous TCR (valid from-to the same) and the all days option was used, it shows properly on the chart, but when the user opens the object from the chart, ECMT shows a huge error message on the object page. It was fixed and no error message is shown.

    Drupal core update

    Delete/remove location

    There is a problem when we delete a location from the system. In this...

    Read more

November 20, 2020

  • 1:57pm
    [ECMT] [Discussions] Máté Bak created 2020.11.20. Sprint review Friday, November 20Máté Bak created 2020.11.20. Sprint review  ReviewSearch bug on stagingThere was an issue with searches that contain a dash (-). The issue has been fixed.The chart does not load on Antwerpen - RotterdamThe chart has time-out when the user would like to filter for the direction on the Antwerpen - Rotterdam line. This is valid for the production system too, but it has been fixed now.Notice after cloningAfter cloning an object and save, we noticed strange error messages that appeared sometimes. We could see that it happens when a location is removed from a line (not when the location is completely deleted).The proposed solution is to act as the location was completely deleted, meaning we keep the record in the timetable, but indicate that there is an unknown location. The solution can come in the next sprint.Criss-cross objects direction problemPA3 and P4 lines cross each other more than once. We were not prepared for such a use case, so far we covered only the case when they crossed each other once. Now, it's fixed, however, in the next sprint, we will think about a general solution for cases like this.Direction filter bugThe user tried to filter for top-bottom direction objects, and some bottom-top direction objects were shown too. We saw that it happened because the from/to locations were changed in those objects, without refreshing the timetable. Now, there is an error message, if the from/to location of the line is not compliant with the first and last location of the timetable. You can see the demonstration of the problem on the following screenshot.On Monday (2020.11.23) the new release will be deployed on production.PlanCriss-crossing objects with offsetGeneral solution for criss-crossing objects (concept)Create preloader information for the cahrt (pörifori)Drupal core updateMáté Bak created 2020.11.20. Sprint review

    [ECMT] [Discussions] Máté Bak created 2020.11.20. Sprint review

    Friday, November 20

    Máté Bak created 2020.11.20. Sprint review

     

    Review

    Search bug on staging

    There was an issue with searches that contain a dash (-). The issue has been fixed.

    The chart does not load on Antwerpen - Rotterdam

    The chart has time-out when the user would like to filter for the direction on the Antwerpen - Rotterdam line. This is valid for the production system too, but it has been fixed now.

    Notice after cloning

    After cloning an object and save, we noticed strange error messages that appeared sometimes. We could see that it happens when a location is removed from a line (not when the location is completely deleted).

    The proposed solution is to act as the location was completely deleted, meaning we keep the record in the timetable, but indicate that there is an unknown location. The solution can come in the next sprint.

    Criss-cross objects direction problem

    PA3 and P4 lines cross each other more than once. We were not prepared for such a use case, so far we covered only the case when they crossed each other once. Now, it's fixed, however, in the next sprint, we will think about a general solution for cases like this.

    Direction filter bug

    The user tried to filter for top-bottom direction objects, and some bottom-top direction objects were shown too. We saw that it happened because the from/to locations were changed in those objects, without refreshing the timetable. Now, there is an error message, if the from/to location of the line is not compliant with the first and last location of the timetable. You can see the demonstration of the problem on the following screenshot.

    On Monday (2020.11.23) the new release will be deployed on production.

    Plan

    • Criss-crossing objects with offset
    • General solution for criss-crossing objects (concept)
    • Create preloader information for the cahrt (pörifori)
    • Drupal core update

    Review

    Search bug on staging

    There was an issue with searches that contain a dash (-). The issue has been fixed.

    The chart does not load on Antwerpen - Rotterdam

    The chart has time-out when the user would like to filter for the direction on the Antwerpen - Rotterdam line. This is valid for the production system too, but it has been fixed now.

    Notice after cloning

    After cloning an object and save, we noticed strange error messages that appeared sometimes. We could see that it happens when a location is...

    Read more

November 6, 2020

  • 12:13pm
    [ECMT] [Discussions] Máté Bak created 2020.11.06. Sprint review Friday, November 6Máté Bak created 2020.11.06. Sprint review  ReviewFinally, the conflict detection implementation is finished and it will be released to staging on the next week. Each object will have a detect overlapping option on the page, where the user can check all the other objects that are overlapping with the selected one.PlanThe supplier was informed about the plans for 2021, focusing mostly on the TTR IT Pilot, for example:Connection to Common InterfaceExtension of objects with additional attributes (especially TCRs)Ability to receive and send XML messages using the TTR XSDAccording to the timeline of the TTR IT Pilot, the system pre-condition shall be ready by June 2021.Máté Bak created 2020.11.06. Sprint review

    [ECMT] [Discussions] Máté Bak created 2020.11.06. Sprint review

    Friday, November 6

    Máté Bak created 2020.11.06. Sprint review

     

    Review

    Finally, the conflict detection implementation is finished and it will be released to staging on the next week. Each object will have a detect overlapping option on the page, where the user can check all the other objects that are overlapping with the selected one.

    Plan

    The supplier was informed about the plans for 2021, focusing mostly on the TTR IT Pilot, for example:

    • Connection to Common Interface
    • Extension of objects with additional attributes (especially TCRs)
    • Ability to receive and send XML messages using the TTR XSD

    According to the timeline of the TTR IT Pilot, the system pre-condition shall be ready by June 2021.

    Review

    Finally, the conflict detection implementation is finished and it will be released to staging on the next week. Each object will have a detect overlapping option on the page, where the user can check all the other objects that are overlapping with the selected one.

    Plan

    The supplier was informed about the plans for 2021, focusing mostly on the TTR IT Pilot, for example:

    • Connection to Common Interface
    • Extension of objects with additional attributes (especially TCRs)
    • Ability to receive and send XML messages using the TTR XSD

    According to the timeline of the TTR IT Pilot, the system pre-condition shall be ready by June 2021.

    Read more

October 22, 2020

  • 10:55am
    [ECMT] [Discussions] Máté Bak created 2020.10.22. Sprint review Thursday, October 22Máté Bak created 2020.10.22. Sprint review  ReviewUse aggregated timetable for conflict detectionWe checked during the demo the following scenarios:Catalog vs. CatalogBand vs. BandBand vs. CatalogTCR vs. BandTCR vs. PathWe have performance issue when we filter for the overlap on station. We have to check that issue, it will be on the next sprint too.It has to be checked, how we call or whether we shall detect the case, when a slot path is overlapping with its own band. Currently, we call it as an overlap on station.Appearance of path with offset on Atlantic lineThe problem disappeared with the update of the line. Anyway, the offset issue is solved. It was there only for the path, but it's fixed now, deployed to staging.Chart render problemTCRs caused the trouble, but it's fixed and deployed on staging.0:00 times for BandsIt was not possible to enter 00:00 for bands in the first row, not it is.Catalog vs. CatalogBand vs. BandBand vs. CatalogTCR vs. BandTCR vs. PathWe have performance issue when we filter for the overlap on station. We have to check that issue, it will be on the next sprint too.It has to be checked, how we call or whether we shall detect the case, when a slot path is overlapping with its own band. Currently, we call it as an overlap on station.Hogy hívjuk azt, amikor a slot catalog átfed a rászerkesztett banddel? Most overlap on station.Appearance of path with offset on Atlantic lineThe problem disappeared with the update of the line. Anyway, the offset issue is solved. It was there only for the path, but it's fixed now.Deployed to stagingMásold be a hibát az e-mailből.Chart render problemTCRs caused the trouble, but it's fixed and deployed on staging.0:00 times for BandsIt was not possible to enter 00:00 for bands in the first row, not it is.Two points crossing line presentation problemI created two lines and paths for each.mba line 1mba line 2They cross each other twice, once at loc2 and once at loc4. According to a recent dev, the path on the line 2 shall not be shown between loc2 and loc3. Check https://ecmt.staging.i0.hu/path/283 on the chart.The problem is fixed now and available on staging.Continuous TCR presentation problemFor one day continuous TCR, the tool showed a wrong presentation (it's shown on the previous picture). Now it's fixed too.Next sprintOverlap on station performance issuePotential conflicts testing with offsetsMultiple-crossing objects with offsetThink about how to work with dense lines -> according to the input on Atlantic pilotAnd we will start the planning for 2021 keeping in mind the TTR IT pilot and the system pre-conditions (such as XML import)Máté Bak created 2020.10.22. Sprint review

    [ECMT] [Discussions] Máté Bak created 2020.10.22. Sprint review

    Thursday, October 22

    Máté Bak created 2020.10.22. Sprint review

     

    Review

    Use aggregated timetable for conflict detection

    We checked during the demo the following scenarios:

    • Catalog vs. Catalog
    • Band vs. Band
    • Band vs. Catalog
    • TCR vs. Band
    • TCR vs. Path

    We have performance issue when we filter for the overlap on station. We have to check that issue, it will be on the next sprint too.

    It has to be checked, how we call or whether we shall detect the case, when a slot path is overlapping with its own band. Currently, we call it as an overlap on station.

    Appearance of path with offset on Atlantic line

    The problem disappeared with the update of the line. Anyway, the offset issue is solved. It was there only for the path, but it's fixed now, deployed to staging.

    Chart render problem

    TCRs caused the trouble, but it's fixed and deployed on staging.

    0:00 times for Bands

    It was not possible to enter 00:00 for bands in the first row, not it is.

    • Catalog vs. Catalog
    • Band vs. Band
    • Band vs. Catalog
    • TCR vs. Band
    • TCR vs. Path

    We have performance issue when we filter for the overlap on station. We have to check that issue, it will be on the next sprint too.

    It has to be checked, how we call or whether we shall detect the case, when a slot path is overlapping with its own band. Currently, we call it as an overlap on station.

    Hogy hívjuk azt, amikor a slot catalog átfed a rászerkesztett banddel? Most overlap on station.

    Appearance of path with offset on Atlantic line

    The problem disappeared with the update of the line. Anyway, the offset issue is solved. It was there only for the path, but it's fixed now.
    Deployed to staging

    Másold be a hibát az e-mailből.

    Chart render problem

    TCRs caused the trouble, but it's fixed and deployed on staging.

    0:00 times for Bands

    It was not possible to enter 00:00 for bands in the first row, not it is.

    Two points crossing line presentation problem

    I created two lines and paths for each.

    • mba line 1
    • mba line 2

    They cross each other twice, once at loc2 and once at loc4. According to a recent dev, the path on the line 2 shall not be shown between loc2 and loc3. Check https://ecmt.staging.i0.hu/path/283 on the chart.

    The...

    Read more