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

Is it okay to have theoretical analysis first in our report? #13

Open
ashleydavies opened this issue Mar 21, 2019 · 1 comment
Open

Comments

@ashleydavies
Copy link

ashleydavies commented Mar 21, 2019

Some elements of the theoretical analysis might come in useful to reference during the empirical analysis, for example:

Aspects you may wish to cover include:

Main processes and data flows
Data and control dependencies
...
Critical path and average parallelism
Asymptotic scaling with the most important parameters
Key bottlenecks which might limit scaling to many parallel tasks

Since it seems to be prompting us to take a wider look at the code base and document what's going on, I think it would be beneficial to have already explained this, so that when it comes to documenting the empirical analysis we can reference our explanations in the theoretical anlysis

Is this okay? Is any particular order enforced in the report?

@jjd06
Copy link
Contributor

jjd06 commented Mar 21, 2019

If your report will make more sense presented this way 'round then sure, go for it.

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