GithubHelp home page GithubHelp logo

cejkaluk / research-assignment-lu-decomposition Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 0.0 49.26 MB

Lower-Upper Decomposition research assignment project that I did during my 1st and 2nd year of the Applications of Software Engineering program at the Faculty of Nuclear Sciences and Physical Engineering the Czech Technical University in Prague.

TeX 21.23% HTML 60.83% CMake 4.57% Shell 0.93% C++ 11.01% Cuda 0.01% Python 1.40% C 0.02%

research-assignment-lu-decomposition's People

Contributors

cejkaluk avatar

Watchers

 avatar

research-assignment-lu-decomposition's Issues

Correct errors in text

There are some errors in the text that should be corrected:

Page Description Correction
13 Cubed symbol in the GPU comparison table Remove the cubed symbol
14 Missing article "the" before "GPU" Add the article
14 Implication that a CUDA kernel is always executed in parallel across several threads Replace "it is executed" with "it can be executed"
15 Missing "if" before "some threads" Add "if"
16 Incorrect statement on what instructions threads will execute in the example Mention that threads 0-3 will also execute statement Z
63 The 2nd equation contains an error and unwanted numbering Replace $z_{ij}$ with $a_{ij}$ and remove the equation numbering
87 Incorrect column title in the table Replace Matrix with Precision

Note: page numbers refer to pages in the Submitted version.

Chapter 2: Implementation

  • Write up draft version
  • Send to Supervisor for checking
  • Finalize chapter based on supervisor's comments
  • Sanitize chapter

Chapter 1: Theory

  • Write up a draft version
  • Send to Supervisor for checking
  • Edit chapter based on supervisor's comments
  • Remove useless comments
  • Sanitize chapter

Check entire thesis - specific points

Check thesis

High priority

  • Refer to the theory later from the results!!! To show that the theory contents were not written for no reason
  • Full stops and commas after equations if the equations are part of a sentence.
  • Citations in text
    • Spaces between text and citations
    • Multiple citations should be in one \cite{} command, not \cite{}\cite{}\cite{}
  • Math font: (double-check in ch1)
    • vectors: small letters
    • matrices:
      • Double-line caps letters (using \mathbb{})
    • Small 'l's consistent font
    • \nonumber\,. should be before newline
  • Code blocks (both in text and in the attachments):
    • All code blocks have the same spacing in code (for( int... i++ ) and not for ())
    • All code blocks have the same formatting of {}. Use either void func_name { \n} or void func_name \n{ \n}
    • All code blocks must have their contents start on the left-most tab, i.e. no spacing from the left part of the listing
  • In-line code: (this and below needs to be checked for ch1)
    • Correct any overflowing in-line code-formatted text.
  • In the text, subsections are referred to as sections -> make this consistent everywhere.
  • All numbers in text must not be in math mode: $ <number> $.
  • All chapter/section/subsection/subsubsection names must have capital letters as the first letters (not any type of paragraphs)
  • Double-check hyphenation:
    • non-zero is not as popular -> use nonzero instead.
    • Replace all sub- words with sub (for example: sub-optimal -> suboptimal - correct according to the Oxford dictionary)
  • All numbers in the thesis should have the thousands either separated with a comma, or not separated -> check BP.
  • Sections, Figures, Tables, etc. must all have a capital letter in text (Section~\ref{}, Figure~\ref{}, Table~\ref{})
  • All quotes, or statements in "" should be italicized.
  • Remove any \TODO or any \TO
  • Check code formatting in all lstlistings envs - correct syntax highlighting

Low priority

  • TiKZ - figures (low priority, can be done after the thesis is finished):
    • Convert as many figures as possible to TiKZ
    • Some TiKZ source code can be found in some papers
    • High priority:
      • Page 53 (it is slightly blurred and the colored background is off-putting)
  • Address and remove TODOs
  • Double-check spelling using TeXstudio and Grammarly
  • Look into removing all empty lines between text in all .tex files containing writing content. For example, the PDF contains larger spaces between the two "text text" and the itemized part if there is the code below. However, the empty lines are not present in the .tex file, then the spaces are smaller in the PDF.

    text text

    \begin{itemize} \end{itemize}

    text text

  • Label names but be consistent:
    • {Type:chapter-section-subsection-subsubsection-paragraph-specific-content-name}
    • No hyphenation in Type, for example, Sub-figure:CUDA-global-memory-non-coalesced-access and Sub-figure:CUDA-global-memory-non-coalesced-access-2 in Chapter 1

Chapter 3: Benchmark Results

  • Write up draft version
    • Include:
      • At the end of Chapter 1: Theory there is a hypothesis mentioned that states that Crout's method may provide less accurate results than its numerical modification as the numerical method may converge to an even better solution due to rounding errors. MENTION in the results if this looks like it could be true (=> more investigation required), or if it is just wrong.
  • Send to Supervisor for checking
  • Finalize chapter based on supervisor's comments
  • Sanitize chapter

Introduction, Conclusion & Abstract

  • Write up the draft introduction and conclusion
  • Send to Supervisor for checking
  • Finalize the introduction and conclusion based on the supervisor's comments
  • Sanitize the sections

Bibliography

  • Find the formatting required by the Software Engineering department
    • See Formulář zadání výzkumného úkolu
    • The closest I could find that, however, doesn't fulfill the requirement of "short first names only" is ISO 690 numeric in citacepro.com
    • Can also try to use BibTeX - see Bookmarks -> ASI Master's -> Vyzkumny ukol -> Bibliography formatting for a set of pages that could help
  • Finalize the formatting of the bibliography - re-order the sources as best as possible to how they appear in text.

Create contents of attached CD

  • Create the contents of the CD that will be attached to the thesis:
    • Benchmark files
    • LU Decomposition repository latest snapshot
    • FInal PDF of the thesis
    • README (.md and .html)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.