ferrall/niqlow_exercises

niqlow_exercises's Issues

Ayagari model

I fixed the problem using AV(a) in FeasibleActions. You will have to checkout the Develop branch of niqlow to use it.

I also figured out the problem. Your FeasibleActions() uses e, which is a Tauchen variable. You have to "Update" the actual values before using them. niqlow does not do this for you because in some cases this could create an error.

Get Nam set up so we can code collaboratively

• . Accept invite
• Then in github desktop, File -> Clone Repository. You should see the repository on the list. Select it to clone (choose a different directory if you want).
• . Notice that I created a subdirectory for each of you in niqlow_exercises. Move your code for Exercise 1 (LSext.ox and LSext_main.ox and anything else) from wherever it is now to that directory.
• . run your code like Nam did. Then Save the output file in your subdirectory so I can see the errors and output without having to run it myself.
• Next, github desktop COMMIT your changes to your fork. When that is complete you will see "Fetch Origin" changes to "Push Origin"
• When all this is done, mark this issue as CLOSED. I will be notified and can look at your code.
  I will make changes that get put up in the repository, and you can see exactly what I changed. I will add comments too. You can then "Fetch" the changed files, work with them, then Push them again for me to look at.

Get Steph setup so we can code collaboratively

• . Accept invite
• Then in github desktop, File -> Clone Repository. You should see the repository on the list. Select it to clone (choose a different directory if you want).
• . Notice that I created a subdirectory for each of you in niqlow_exercises. Move your code for Exercise 1 (LSext.ox and LSext_main.ox and anything else) from wherever it is now to that directory.
• . run your code like Nam did. Then Save the output file in your subdirectory so I can see the errors and output without having to run it myself.
• Next, github desktop COMMIT your changes to your fork. When that is complete you will see "Fetch Origin" changes to "Push Origin"
• When all this is done, mark this issue as CLOSED. I will be notified and can look at your code.
  I will make changes that get put up in the repository, and you can see exactly what I changed. I will add comments too. You can then "Fetch" the changed files, work with them, then Push them again for me to look at.

Next round

There is a new branch of the exercises for each of you.

• In Github Desktop, click on "Fetch origin." Look under "Current branch"

• If you select the branch with your name it will "check out" the changes I made up on github. If you now open the files in OxEdit you will see my version. You can also compare with your versions to see the "deltas" (differences) between the main branch and the current branch. You can do this inside Github Desktop or on github.com. So you can see where I deleted lines or modified them along with some Ox comments for explanation.

• Your jobs now are to try again with the new version that fixes some problems but maybe not all of them.

• Then commit changes (including new output file) and Push them to the origin.

• When you have done this, comment on this issue explaining your problem. I'll be notified of the comment and will keep the process moving until eventually your code appears correct ...

struct/class: One of you asked about the difference between "struct" and "class." They are almost identical/interchangeable, and for your code I don't think it matters which one you use. I'll demo the difference tomorrow.

Indentation of Code

From now on, I am going to insist that you follow SOME formatting style for your code.
At the minimum, you must indent (using TAB) code that is inside brackets.

My own personal style is this: https://en.wikipedia.org/wiki/Indentation_style#Ratliff_style

But as you can see from that wiki page that is not the only possibility. (Until just now I didn't even know it had a name, it was the format that makes sense to me.)

From now on, if you submit code that does not indent or does not follow some style that I can discern I will not help with your code. And you probably need help to pass the class!

Why tabs and not spaces? See https://www.youtube.com/watch?v=SsoOG6ZeyUI