Skip to content

Conversation

@robert-vogel
Copy link
Contributor

I wanted to use the nice command line interface made available by the STITCH.R script when testing phasing. To do this I've added an option, doPhasing, and made the necessary changes to STITCH/STITCH/R/functions.R to account for this change. I hope it is helpful!

Robert Vogel added 4 commits July 1, 2025 07:14
…produced to directory . I also recommend, and have implemented, to stop tracking release. Couldn't one just use git tags and the release structure in GitHub?
…ify option. I also changed user facing options from do_phasing to doPhasing to maintain camel case option specification. I then updated the STITCH function in to accomodate this change. I left internal function to use do_phasing so not to break functionality.
There have been updates to the master branch since I started making my
simple changes.
@Zilong-Li
Copy link
Collaborator

Thanks @robert-vogel,

Btw, did you just replace the old option do_phasing with doPhasing? Do you have a more strong argument for this change other than being opinionated? We'd like to avoid breaking changes unless necessary.

Zilong.

@robert-vogel
Copy link
Contributor Author

robert-vogel commented Jul 22, 2025

Hi @Zilong-Li,

The update is just adding doPhasing to the STITCH.R script for using STITCH from the command line. The remaining changes were, for the most part, in service to that option. I changed the variable from snake case to camel case because it seemed that most of the variables presented to the user were in camel case, see lines 92-315 in the STITCH.R script. Personally, I have no preference in variable naming conventions, so-long as the convention is consistent.

If you prefer snake case for do_phasing, I am happy to make that update. I don't want to make any more work for you with such a trivial update.

best,

Robert

@Zilong-Li
Copy link
Collaborator

Ah, sorry I overlooked the CLI part in this PR. Would be appreciated if you can use snake case for do_phasing.

Thanks,
Zilong

@robert-vogel
Copy link
Contributor Author

No problem. I'll work on the update to snake case today.

Thanks,
Robert

@rwdavies
Copy link
Owner

Hi, sorry for my slow reply I'm on parental leave and have also been on vacation for most of the last three weeks.

The inconsistency in camel case vs snake case is probably mostly my fault as I've bounced around various settings that have used one or the other and haven't been consistent here. I don't think it matters much.

I guess a more key question - does the phasing work? I imagine I wrote this code many years ago, and I can't quite remember what I would have done, and how accurate it was? @robert-vogel have you tested it?

@robert-vogel
Copy link
Contributor Author

Hi @rwdavies, congratulations on your new family member (in response to parental leave)! The code runs smoothly, but I haven't yet computed the switch error rate on our data. I expect to do this in the next month or so, as I am trying to solve a different challenge. I'm happy to share the results with you once they are generated.

@Zilong-Li Still need to update the variable name case, I'll do that soon, just got busy with other stuff.

@robert-vogel
Copy link
Contributor Author

I just now got back to this. I updated the names as requested. If you, @Zilong-Li , didn't already add do_phasing to STITCH command line script, this may be of use.

@Zilong-Li Zilong-Li merged commit c7e79f5 into rwdavies:master Oct 10, 2025
6 checks passed
@Zilong-Li
Copy link
Collaborator

Thank you Robert!

@robert-vogel robert-vogel deleted the phasing branch November 5, 2025 11:27
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

Successfully merging this pull request may close these issues.

3 participants