Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Meeting Info

AI/ML Framework meetings are open to the public and held on Tuesdays at noon UTC.  World Time Zone Map

Zoom 1 Info:

UTC-timeTuesday 12:00 (Summer)
Tuesday 13:00 (Winter)

https://zoom.us/j/9644759813

Seoul (KST / UTC+9)Tuesday 21:00Tuesday 22:00TODO
Delhi (IST / UTC+5:30)Tuesday 17:30Tuesday 18:30TODO
Seattle (PST / UTC -8)Tuesday 04:00

New York (EDT / UTC -4 during DST (-5 in the winter))Tuesday 08:00Tuesday 09:00+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)
Beijing (CST / UTC+8)Tuesday 20:00Tuesday 21:00+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)
Tokyo (JST / UTC+9) Tuesday 21:00Tuesday 21:00+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)
Other international numbersWorld Time Zone Map

International numbers available: https://zoom.us/u/acyy3hylQi


All meeting notes

...

2024-

...

11-

...

26 (Tuesday) Next Meeting:  

Recording link: TBD


    • Pip package for SDKs, discussion ongoing with LFIT.
    • Model Performance measurement
      Jira Legacy
      serverSystem Jira
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyAIMLFW-91
  • Bugs/feature (Recent merge /WIPhttps://
      • repository has been created
      • Builds are failing (raised to LF)
    • Import the code related to UAV path prediction use case to repository 
      • version code management.

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan

2024-11-26 (Tuesday) : Cancelled

2024-10-15 (Tuesday) :  

Recording link: https://zoom.us/rec/share/5mPnHMzmPc164qTRRtQ4odQjWaO8koBnb1BVXCWAi635f2t1NLrvFxGF2fNoy1TF.NpYLuUd9VdocC04J

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan

2024-10-01 (Tuesday)

Recording link: https://zoom.us/rec/share/8Ilxz99L_zX0BJ6ZkLAxoR-z3Gor9m1EFlQtpmXWXU1KLef4J848UuHw6aVhJFqq.uP1-2nqPh0AwlKBa

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan

2024-09-17 (Tuesday)

Recording link: https://zoom.us/rec/share/lMXR7SSB3r9MBuHcJ12PvrU3YreTJAfwjk-NwivW4nRK9NyJHL1-eGLBTepeZIa5.iC04E57oIKb1efjn

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan

2024-09-03 (Tuesday)

Recording link: https://zoom.us/rec/share/pU7-ybDl_-Lha4bWE1Fn9Ybslv7i-y5y6je9TXpVR6q8UekoB1TQevmc9I_T12Gs.dBMp5kvH4JGQ-dYl

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan
  • Repository needed for model performance [Subhash] 
  • update comments from last meeting on model performance:
    • Step 1 dev: have influx DB within AIMLFW and Y1 consumer will push the performance parameter to it.
    • Step 2 dev: Integrate with nonRT RIC as performance data producer.

...

Action Item:

  • Identify the AIMLFW expectation from integration test [any use case]
  • Pairwise testing plan
  • Repository needed for model performance – 
  • update comments from last meeting on model performance [Subhash]

...

  • Topics:
    • Model Performance measurement
      Jira Legacy
      serverSystem Jira
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyAIMLFW-91
    • Bugs
    • Support asked: 
      • Jira Legacy
        serverSystem Jira
        serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
        keyAIMLFW-109
    • Integration of AIMLFW with NonRT RIC
    • First time contributor
      • JunHyuk Lim
      • GyuYong Park
      • Kim Do Young
      • inni
      • Sumin Im

...

  • Joseph Thaliath presented the I release plan. Summary and more details are there in the "I" Release page.
  • Joseph Thaliath mentioned that if anyone is interested to discuss on those topics or willing to contribute, please send an email to jo.thaliath@samsung.com
  • @Navaneethan asked about the pre-processing step that is required before training the model. How is it handled or it is assumed it will not be there ?
  • Joseph Thaliath mentioned that in the current framework it can be handled as part of training pipeline or limited instructions for data transformation can be given to data extraction component. But it is not clear how it is handled from O-RAN alliance point of view.
  • @Navaneethan asked if  we are storing the model in the pickle format or any other form recommended?
  • Joseph Thaliath mentioned that the framework is transparent to the format, any format, the model sdk zip the file/folder in Model DB. We are assuming the entity using the model knows how to use the model after unziping
  • Deeepanshu Karnwal asked if continuous training flow is supported?
  • Joseph Thaliath mentioned that the current framework supports only one time offline training and if training is required again, it needs to be triggered again using the training API. There is no option to currently use previous model for further training.
  • SANDEEP KUMAR JAISAWAL mentioned that the current framework has option to trigger training API again and again but the only thing that we are not doing is retaining as soon as the new set of data is available.
  • John Keeney (Ericsson EST) mentioned that there will some changes in the interface used by AIMLFW for the H-release maintenance
  • Kevin Timoney will clarify the changes in the interface used by AIMLFW  by email.
  • Joseph Thaliath will look at these changes and see if it can be integrated easily and if there are any queries will contact Kevin or John.

...