combining CoR and CoP reports

[nhejazi]

per prior discussions, we should migrate to a revised format in which the CoR and CoP reports are unified, allowing for both sets of results to be presented in a single deliverable. the work required for this should be very limited, as the currently defunct CoP report only contained results of the analyses conducted in cop_stochastic and cop_mediation.

[nhejazi]

any thoughts on this for further discussion @benkeser @youyifong?

[youyifong]

Hi Nima, thanks for bringing this up. I have a related question. The way the readme is currently written envisions a choice of analyses. At this point, to add or remove a chapter to, say, the CoR report, we would change index_cor.yml and Makefile. This works fine, but I wonder if there is a more elegant way, which may even remove the need for all the analysis-specific index_xxx.yml files. Best, Youyi

…

On Tue, Nov 9, 2021 at 8:48 AM nima hejazi ***@***.***> wrote: any thoughts on this for further discussion @benkeser <https://github.com/benkeser> @youyifong <https://github.com/youyifong>? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBH5L4DESB3GA4FA6O3MX3ULFGD7ANCNFSM5HVYOCQA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nhejazi]

Thanks for your thoughts on this, Youyi. In a repository with only the stochastic VE analyses, I've been experimenting with a format that may allow for something like this. Worth discussing in the future, but I'd like to see the individual project subdirectories and report transition to using the orderly format for reproducibility, which would have the added benefit of allowing archiving of reports and their artifacts. If we have these stored, then it would really just be a matter of allowing for flexible inputting of report components via prebuilt make recipes. This might remove some of the redundancies that we had initially introduced through the index_*.yml files.

[youyifong]

Very cool!

…

On Tue, Nov 16, 2021 at 12:24 PM nima hejazi ***@***.***> wrote: Thanks for your thoughts on this, Youyi. In a repository with only the stochastic VE analyses, I've been experimenting with a format that may allow for something like this. Worth discussing in the future, but I'd like to see the individual project subdirectories and report transition to using the orderly format <https://github.com/vimc/orderly> for reproducibility, which would have the added benefit of allowing archiving of reports and their artifacts. If we have these stored, then it would really just be a matter of allowing for flexible inputting of report components via prebuilt make recipes. This might remove some of the redundancies that we had initially introduced through the index_*.yml files. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBH5L4UWKNLKHD3EBWCTHDUMK4WXANCNFSM5HVYOCQA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.