more details
After the new assignment is released:
for generating framework
| - Please first take a look at the completed PSet solutions for PSet 1 in `sol1.ipynb` for reference.
- Given the screenshots of the PSet, please generate the framework (arrangement of cells) for the PSet solution in this file, so that the subsequent solution contents can be added/fitted in to the cells.
- Please not yet generate the solution contents for the PSet, just the framework.
- For each cell that you generate, please add a comment in the cell to indicate what the cell is for, e.g., "Write solution for this problem." or "Write solution for this part." Also retain the clear instructions from the PSet in the cell so that you know how to solve the problems in the subsequent steps.
- Please add clear instructions to the appropriate cells so that one can fully understand the assignment, which will be used for future solution-generation-process.
- for all markdown-type cells, if there is any bullet point or a series of bullet points, make sure the first line of the bullet points has a blank-line-gap from the previous line of content, or else mkdoc cannot properly render the bullet points. This rule also applies to any ordered-list.
- Be sure to strictly obey the indentation rule, i.e., indentations should be a multiple of 4-space-characters.
- If a sentence or paragraph (can contain math expressions) or a display-math expression belongs to a bullet point, it should be indented by 4-space-characters relative to that bullet point. Same rule applies to ordered-list.
- Please keep the code cell with the comment "# Prepare the environment" intact since it does the necessary imports and environment preparation. You can append your generated cells below this cell.
- For all markdown-type cells, for all levels of headings, please make sure there is no math expression in the heading, otherwise mkdoc will not render the math expression properly.
- Please take `sol1.ipynb` as reference and modify your wordings in the cells: use something like "a. " but not "Part a:" or "Part (c)" which is consistent in style as `sol1.ipynb`. Same rule applies to higher level of headings such as a1, a2, b6, b7, ...etc.
|
For your generated output:
- for all markdown-type cells, if there is any bullet point or a series of bullet points, make sure the first line of the bullet points has a blank-line-gap from the previous line of content, or else mkdoc cannot properly render the bullet points. This rule also applies to any ordered-list.
- Be sure to strictly obey the indentation rule, i.e., indentations should be a multiple of 4-space-characters.
- If a sentence or paragraph (can contain math expressions) or a display-math expression belongs to a bullet point, it should be indented by 4-space-characters relative to that bullet point. Same rule applies to ordered-list.
- For all markdown-type cells, for all levels of headings, please make sure there is no math expression in the heading, otherwise mkdoc will not render the math expression properly.
- You can safely use Latex expressions like
\ket{} or \bra{} since I have already imported the physics package into Mathjax
- For each problem's title, use second-level header in bold such as the sameformat as
## **Problem 2-1 []**, don't fill in anything into the middle bracket [] and leave it blank as I will manually fill in values into it after. Also for each part within the same problem, use the third-level headers in bold such as ### **a. []**.
-
Obey to what the image shows when I ask you to do text recognition. i.e., if it's inline math in the image, then output: $inline-math-blablabla$. If it's display math (block math), then output
```
\[
block-math-blablabla
\]
```. (notice that for block math, the pair of 2-dollar signs each have their own line, the wrapped content starts in a new line, and the entire block has a margin of 1 blank line in both top and bottom.)
-
Please only use the single- and double- dollar signs for Latex expressions, do not use \( or \[.
- If the original text does not start from a newline, then don't change to a new line by yourself.
for generating solutions
| - Write solution for this problem or sub-problem.
- for all markdown-type cells, if there is any bullet point or a series of bullet points, make sure the first line of the bullet points has a blank-line-gap from the previous line of content, or else mkdoc cannot properly render the bullet points. This rule also applies to any ordered-list.
- Be sure to strictly obey the indentation rule, i.e., indentations should be a multiple of 4-space-characters.
- If a sentence or paragraph (can contain math expressions) or a display-math expression belongs to a bullet point, it should be indented by 4-space-characters relative to that bullet point. Same rule applies to ordered-list.
- For all markdown-type cells, for all levels of headings, please make sure there is no math expression in the heading, otherwise mkdoc will not render the math expression properly.
- When generating solutions, you may take all the files within folder (which are previous solutions from the same course in the past years) as reference, though you need not follow them strictly since the numbers in the latest-version problems may be slightly tweaked, or some solutions may be slightly wrong.
|
for jupyter notebook polishing
| Please edit my entire #file:sol1.ipynb so that:
- each code cell is more clean and succinct, but their output will remain exactly the same after changing the codes.
- you can modify all kinds of thing, e.g., code structure, function name, ...code style, ...etc, to meet the academic or industrial standard and make it easy and clear to understand without taking up too much lines of codes.
- you can first list out your plan of code-modification in big picture, and then follow your guide points and do the revising step by step.
- you may as well modify the markdown-type cells if needed. But please just reduce the unnecessary redundancies, not cutting all the details.
|