Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Openctest and IDoCT #30

Open
tianyin opened this issue Jul 3, 2023 · 2 comments
Open

Openctest and IDoCT #30

tianyin opened this issue Jul 3, 2023 · 2 comments
Assignees

Comments

@tianyin
Copy link
Member

tianyin commented Jul 3, 2023

@Alex-Lian I have a question about OpenCtest and IDoCT.

How are they related? It seems to me that it is odd that we are keeping two separate copies of the same repo? Is there a way to merge these two repos (e.g., OpenCtest as a git submodule as IDoCT)?

@xylian86
Copy link
Collaborator

xylian86 commented Jul 3, 2023

@tianyin From my perspective, the OpenCtest repo is initially the artifact of the ctest paper, which includes several folders to reproduce the results in the paper. And now it has become the core of our configuration-related research, including projects such as uRTS and confuzz.
On the other hand, the IDoCT repository was originally created as part of the tasks for 591 SE & REU. Our aspiration was for this repository to bolster our research, although it seems to have not yet served this purpose. And IDoCT is an extension of the OpenCtest repository.

I remember we discussed whether to reuse the OpenCtest repo instead of creating a new repo (IDoCT), the conclusion is that the OpenCtest repo is too heavy as it contains many scripts to reproduce the results of paper. And for the onboarding task, we only need a small set of the scripts.

@tianyin
Copy link
Member Author

tianyin commented Jul 3, 2023

Thanks for the explanation @Alex-Lian !

I forgot the rationale and you helped me to page it back.

although it seems to have not yet served this purpose

We will get there. I chatted with @owolabileg and he is equally excited about it (we should loop him in when we decide to pursue the research).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants