You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- $\begingroup$ The approach in the paper that you reference is indeed very interesting and close to our paper. However, they use a $VAR(1)$ mode, in which auto-correlations do not vanish but just decay. We chose a $VMA(1)$ model as there the autocorrelations vanish after one time step. If autocorrelation comes from non-contemporaneous trading then it should vanish after one day. In practice a $VMA(1)$ and a $VAR(1)$ model will give similar results in most applications. $\endgroup$Richi Wa– Richi Wa2013-04-03 08:57:31 +00:00Commented Apr 3, 2013 at 8:57
- $\begingroup$ I tend to shy away from moving average models and just increase the number of lags in a autoregressive model, but what you're saying makes sense. $\endgroup$John– John2013-04-03 13:38:34 +00:00Commented Apr 3, 2013 at 13:38
- $\begingroup$ Just one more and last comment: if you look at the preprint above page 5 formula 1.6 then you see how the regression of returns on lagged returns is represented. This looks at first glance like $VAR(1)$ but when you analyze the residual then this can not be shown to be White Noise, which it should be for $VAR(1)$. $\endgroup$Richi Wa– Richi Wa2013-04-04 07:20:25 +00:00Commented Apr 4, 2013 at 7:20
- 1$\begingroup$ I don't keep my promise, one more comment: you are right, that the calibration of $VAR(1)$ is more intuitive (it cna be done by a regression) than the calibration of $VMA(1)$. Our experiments in this context gave good results for the calibration of $VMA(1)$ too. $\endgroup$Richi Wa– Richi Wa2013-04-04 07:41:57 +00:00Commented Apr 4, 2013 at 7:41
- $\begingroup$ I've read about the use of a garch process, what do you thik about it ? $\endgroup$Lucas Morin– Lucas Morin2013-04-11 13:43:04 +00:00Commented Apr 11, 2013 at 13:43
| Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. option-pricing), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
default