You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Some elements of the theoretical analysis might come in useful to reference during the empirical analysis, for example:
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?
The text was updated successfully, but these errors were encountered: