cwrap.py and pwrap.py are triplicated across demo/ ratc/ tools/ and the demo/ratc copies still use http:// with the api key in the URL

[avinxshKD]

We have cwrap.py in demo/, ratc/, and tools/.., three copies of basically the same file. same story for pwrap.py. The demo and ratc versions are copy-pastes of each other with one line different.

The bigger problem: demo/ and ratc/ both POST to http://www.controlcore.org/pm/{yuyu}{apikey} plaintext HTTP with the API key sitting in the URL. tools/ was updated to https at some point but nobody backported it

Also pwrap.py was never properly cleaned up when cwrap.py was cwrap got context managers and specific exceptions, pwrap still has bare open() calls leaking handles every loop iteration and bare except: everywhere catching KeyboardInterrupt.

One more: if the first POST comes back empty (len(r.text)==0), variable t is never assigned but while oldt==t runs right after that's a NameError waiting to happen.

These six files should be one shared module with cwrap/pwrap as thin wrappers around it.

[avinxshKD]

@pradeeban @Rahuljagwani what do you think about this?? I'll work on this, plan is to extract the shared config/request logic into a single module and have cwrap/pwrap wrap it, fix the http-https backport and clean up the handle leaks in pwrap while I'm at it.

[pradeeban]

@avinxshKD Folders such as ratc/ are examples/samples that built using concore. Not really worth your time as long as they are not broken. These examples were mostly developed for the two concore journal papers (IEEE Access and CLUSTER). Might be a smarter strategy to simply create newer examples/samples that can be presented in a new research paper. A lot of applicants are spending a lot of time and effort on the examples. I am trying to dissuade them from doing that by posting this comment across several PRs.

[avinxshKD]

@pradeeban that makes sense, I'll leave the example folders alone. thanks for the heads up and

btw, would a concore watch CLI command for live simulation monitoring be useful? I can add it to the existing CL (i was thinking about it)

[pradeeban]

If the new features are in new files or at least new functions with minimal changes to existing files (or at least existing features), that will be perfect.

concore is a research framework and we have had 3 papers out of it (all 3 with GSoC contributors from 2021, 2022, 2023, and 2025 as co-authors). I see the GSoC 2026 with Julia having a research potential too.

[avinxshKD]

@pradeeban got it, I’ll keep changes minimal as always, implement this as a new CLI command, and start working on it tday

great context, will keep this CLI addition focused and paper-friendly (new command, minimal core changes), then share a PR you can evaluate for research usefulness

[pradeeban]

@avinxshKD also pls pay attention to the bug report headers. VS Code and its variants (such as Google Antigravity) are making ugly headers. I am fixing this one for you.

[avinxshKD]

@pradeeban thanks for fixing that, I’ll double-check the bug report headers from my side before posting next time