ambropo / var-toolbox Goto Github PK

Hi Dr. Ambrogio Cesa-Bianchi,

I found that the functions called by unitroot.m are missing.
I believe they can be downloaded at here.

Thanks for your great work.

Mark Song

Hi, the toolbox has some 8-9 folders of code; but it seems that all the content of all of those is required to run the single VARToolbox_Primer.m script; it calls codes written in all of those.
i.e. I am having issues with the recognition of Date2Num and vnames so maybe getting all the ancillary routines are needed to make the programme run.
Is there a high-level link for installation of the whole package?
Many thanks in advance, the tool looks really promising.

The current directory for the source code takes the name of what looks like the current version release, v3dot0. Another folder contains old files, OldVersions/v2dot0. I think that it is more standard to have such folders named uniquely, using branches and subsequent releases to keep track of versions. I would suggest the following:

• 1. Pinpoint the name of the source code directory, e.g., src or VAR-Toolbox or var, etc.
• 2. Keep track of different versions with Github branches and releases, a version-control-aware way, instead of relying on old versions folders. This is standard in the Python ecosystem I'm familiar with, but seems the case also for Matlab plugins. This could be done as follows:
  • 1. Using git, create a new local branch called something like v 2.0, which would contain the content of the folder OldVersions/v2dot0, but putting it all in a src folder, thus deleting the "new stuff" now in v3dot0.
  • 2. Push the local branch to a remote branc, so that this v 2.0 branch will be created on Github too.
  • 3. Create a Github release from such branch. This is a bundle that can include just the branch itself with a more prominent tagging (remote branches can be deleted, while releases are preserved) as well as zipped files, etc.
• 3. Repeat steps a.-c. for v.3.0 accordingly, i.e., in this case, if appropriate, deleting OldVersions/v2dot0 and just keeping the v.3 stuff.

Happy to open PRs with steps a. b. for both versions, while the repo owner needs to make the release, which will appear on the right menu of the main repository page and here.

Dear authors

I'm trying to replicate this paper from CESifo:

https://www.cesifo.org/en/publications/2014/working-paper/effectiveness-and-transmission-ecbs-balance-sheet-policies

In here, they use a combination of zero sign restrictions and negative/positive sign restrictions. Is it possible to do it in this toolbox?

Someone might have accidentally pressed TAB and split the TABLE variable name into TAB LE.

https://github.com/ambropo/VAR-Toolbox/blob/9fe5d763da307cdded2827851325766b3a7c60e1/v3dot0/Primer/VARToolbox_Primer_v1.m#L92C7-L92C7