Week 1

July 31th 2023

• Was explained YOLO workflow of AI3
• Details on Pipe-breaks models - Calgary, cox-ph (check pipe-breaks-transfer-learning)
  • It is in form of Algorithm and Utility
• Look into pd.get_dummies() and determine how [a, b, c] and [a, c, b] get assigned integer values, as part of one-hot encoding.
  • The proof is done in the notebook. It is available at https://github.com/gqc/notebooks/nbs/test/test-encoding.ipynb.
• Add documentation on the gqc/notebooks-from-colab/rename_titles.sh used for replacing titles inside notebooks with file names.
• Deployed shell script to github

Aug 1st 2023

1. CoxPH prediction usage
2. Understanding flow of loe-coe, pipe breaks, pipe breaks transfer learning

Aug 2nd 2023

• Move files from Gateway to HP laptop.
• Push gqc-utility changes and raise a PR.
  • PR opened here and merged.
• Include about nbdev CI failing when notebooks have outputs in general.gqc.com/dev/Python/nbdev.
• Look and update CCTV data documentation based on current data structure. Also update cctv workflow documentation.
  • PR opened here and merged.
• To discuss:
  • Need to look into the portability of models (pickled or not)

Aug 3rd 2023

• Sudhir explained models usage in loe-coe-app, pipe-breaks and pipe-breaks-transfer-learning.
• Created and took note on some of the environments to be used for pipe-breaks related repositories on HP laptop, WSL and MSI.
• Set-up and project related files exploring on the laptop.
• Running pipe breaks repositories to get predictions, currently with cox_cgy model.
• Asked Vannary for models other than calgary. She replied with this -> VS_Research/pipe_breaks/saved_models/other utilities base covariants.

Aug 4th 2023

All the notes has been updated in https://projects.gqc.com/project/Pipe%20Breaks/

• To-Do:
  • Change typos and edit the document here.
  • Update low-coe README with details on what is happening, include flow and transfer learning details here.
  • Fix the script_runner.py in loe-coe to run correctly.
    • check .toml files reference issue and fix it, document it in the README
    • Fix the shell script new line bug while it is created.
  • Document where to find the documentation for projects in the README
  • Run pipe-breaks in local using(pipe_breaks) and understand the workflow for cox-dnv or cox-cgy.
  • Test the other utility models Vannary provided using pipe-breaks.
  • Look into the deven-fork and uncommitted changes in local.
  • Add to the rdp docs - blank screen can be resolved if we log out of the msi
  • create another user - gqc_rdp (discuss with jake) - We have hydrotrek user