Merge pull request #57 from QuantEcon/issue36

Issue36

Author: Alim-faraji

lectures/dynamic_programming/wald_friedman.md

@@ -520,9 +520,6 @@ tags: [remove-cell]
     α, β, outcomes, costs, trials = simulation(Problem(return_output = true))
     @test α ≈ 0.57428237
     @test β ≈ 0.352510338
-    @test mean(outcomes) ≈ 0.5
-    @test mean(costs) ≈ 1.28 atol = 1e-2
-    @test mean(trials) ≈ 1.41 atol = 1e-2
     choices = first.(choice.((clamp(β - eps(), 0, 1),
                               clamp(β + eps(), 0, 1),
                               clamp(α - eps(), 0, 1),

lectures/getting_started_julia/getting_started.md

@@ -88,7 +88,7 @@ Otherwise, you can let `IJulia` install its own version of Conda by following [t
 (clone_lectures)=
 ### Starting Jupyter
 
-Next, let's install the QuantEcon lecture notes to our machine and run them (for more details on the tools we'll use, see our lecture on {doc}`version control <../more_julia/version_control>`).
+Next, let's install the QuantEcon lecture notes to our machine and run them (for more details on the tools we'll use, see our lecture on {doc}`version control <../software_engineering/version_control>`).
 
 1. Install [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git/).
 1. (**Optional, but strongly recommended**) Install the [GitHub Desktop](https://desktop.github.com/).
@@ -144,7 +144,7 @@ And open the {doc}`Interacting With Julia <../getting_started_julia/julia_enviro
 If you have access to an online Julia installation, it is the easiest way to get started.
 
 Eventually, you will want to do a {ref}`local installation <jl_jupyterlocal>` in order to use other
-{doc}`tools and editors <../more_julia/tools_editors>` such as [Atom/Juno](http://junolab.org/), but
+{doc}`tools and editors <../software_engineering/tools_editors>` such as [Atom/Juno](http://junolab.org/), but
 don't let the environment get in the way of learning the language.
 
 (jl_jupyterhub)=

lectures/software_engineering/need_for_speed.md

@@ -505,7 +505,7 @@ The main Julia package for benchmarking is [BenchmarkTools.jl](https://www.githu
 
 Below, we'll use the `@btime` macro it exports to evaluate the performance of Julia code.
 
-As mentioned in an {doc}`earlier lecture <../more_julia/testing>`, we can also save benchmark results to a file and guard against performance regressions in code.
+As mentioned in an {doc}`earlier lecture <../software_engineering/testing>`, we can also save benchmark results to a file and guard against performance regressions in code.
 
 For more, see the package docs.
 

lectures/software_engineering/testing.md

@@ -77,7 +77,7 @@ The result should be
 This is all we need for now.
 
 
-**Note:** Before these steps, make sure that you've either completed the {doc}`version control <../more_julia/version_control>` lecture or run.
+**Note:** Before these steps, make sure that you've either completed the {doc}`version control <../software_engineering/version_control>` lecture or run.
 
 ```{code-block} julia
 git config --global user.name "Your Name"
@@ -187,7 +187,7 @@ You can see the change reflected in our default package list by running
 ] st
 ```
 
-For more on the package mode, see the {doc}`tools and editors <../more_julia/tools_editors>` lecture.
+For more on the package mode, see the {doc}`tools and editors <../software_engineering/tools_editors>` lecture.
 
 ### Using the Package Manager
 
@@ -293,7 +293,7 @@ Here's the `Manifest.toml`
 
 We can also run other operations, like `] up`, `] precompile`, etc.
 
-Package operations are listed in detail in the {doc}`tools and editors <../more_julia/tools_editors>` lecture.
+Package operations are listed in detail in the {doc}`tools and editors <../software_engineering/tools_editors>` lecture.
 
 Recall that, to quit the active environment and return to the base `(v1.1)`, simply run
 
@@ -642,7 +642,7 @@ This shows us precisely which methods (and parts of methods) are untested.
 
 ## Pull Requests to External Julia Projects
 
-As mentioned in {doc}`version control <../more_julia/version_control>`, sometimes we'll want to work on external repos that are also Julia projects.
+As mentioned in {doc}`version control <../software_engineering/version_control>`, sometimes we'll want to work on external repos that are also Julia projects.
 
 * `] dev` the git URL (or package name, if the project is a registered Julia package), which will both clone the git repo to `~/.julia/dev` and sync it with the Julia package manager.
 
@@ -694,7 +694,7 @@ Here, for example, we're revising the README.
 
 * Clicking "commit to master" (recall that the checkboxes next to each file indicate whether it's to be committed) and then pushing (e.g., hitting "push" under the "Repository" dropdown) will add the committed changes to your account.
 
-To confirm this, we can check the history on our account [here](https://github.com/quanteconuser/Expectations.jl/commits/master); for more on working with git repositories, see the {doc}`version control <../more_julia/version_control>` lecture.
+To confirm this, we can check the history on our account [here](https://github.com/quanteconuser/Expectations.jl/commits/master); for more on working with git repositories, see the {doc}`version control <../software_engineering/version_control>` lecture.
 
 ```{figure} /_static/figures/testing-expectations.png
 :width: 100%
@@ -708,7 +708,7 @@ The green check mark indicates that Travis tests passed for this commit.
 :width: 100%
 ```
 
-For more on PRs, see the relevant section of the {doc}`version control <../more_julia/version_control>` lecture.
+For more on PRs, see the relevant section of the {doc}`version control <../software_engineering/version_control>` lecture.
 
 For more on forking, see the docs on [GitHub Desktop](https://help.github.com/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/) and [the GitHub Website](https://guides.github.com/activities/forking/).
 
@@ -763,7 +763,7 @@ Another goal of testing is to make sure that code doesn't slow down significantl
 
 We can do this using tools provided by the `BenchmarkTools.jl` package.
 
-See the {doc}`need for speed <../more_julia/need_for_speed>` lecture for more details.
+See the {doc}`need for speed <../software_engineering/need_for_speed>` lecture for more details.
 
 ## Additional Notes
 

lectures/software_engineering/tools_editors.md

@@ -120,7 +120,7 @@ The most feature-rich one for Julia development is [Atom](https://atom.io/), wit
 
 There are several reasons to use a text editor like Atom, including
 
-* Git integration (more on this in the {doc}`next lecture <../more_julia/version_control>`).
+* Git integration (more on this in the {doc}`next lecture <../software_engineering/version_control>`).
 * Painless inspection of variables and data.
 * Easily run code blocks, and drop in custom snippets of code.
 * Integration with Julia documentation and plots.
@@ -274,7 +274,7 @@ Julia's package manager lets you set up Python-style "virtualenvs," or subsets o
 This way, you can work with (and specify) the dependencies (i.e., required packages) for one project without worrying about impacts on other projects.
 
 * An `environment` is a set of packages specified by a `Project.toml` (and optionally, a `Manifest.toml`).
-* A `registry` is a git repository corresponding to a list of (typically) registered packages, from which Julia can pull (for more on git repositories, see {doc}`version control <../more_julia/version_control>`).
+* A `registry` is a git repository corresponding to a list of (typically) registered packages, from which Julia can pull (for more on git repositories, see {doc}`version control <../software_engineering/version_control>`).
 * A `depot` is a directory, like `~/.julia`, which contains assets (compile caches, registries, package source directories, etc.).
 
 Essentially, an environment is a dependency tree for a project, or a "frame of mind" for Julia's package manager.

lectures/software_engineering/version_control.md

@@ -317,7 +317,7 @@ A PR requests the project maintainer to merge ("pull") changes you've worked on
 
 There are a few different workflows for creating and handling PRs, which we'll walk through below.
 
-**Note:** If the changes are for a Julia Package, you will need to follow a different workflow -- described in the {doc}`testing lecture <../more_julia/testing>`.
+**Note:** If the changes are for a Julia Package, you will need to follow a different workflow -- described in the {doc}`testing lecture <../software_engineering/testing>`.
 
 (web_interface)=
 ### Quick Fixes
@@ -476,7 +476,7 @@ At which point the process of creating a PR is identical to the previous case.
 
 One special case is when the repo in question is actually a Julia project or package.
 
-We cover that (along with package workflow in general) in the {doc}`testing lecture <../more_julia/testing>`.
+We cover that (along with package workflow in general) in the {doc}`testing lecture <../software_engineering/testing>`.
 
 ## Additional Resources and Troubleshooting