|
PureBytes Links
Trading Reference Links
|
Also - Tomasz trumped me, as usual, because he has listened to all of
our comments (we discussed all of this stuff in depth in the UKB
committee meetings as well as here) and his reponse was to start
producing videos.
His perception is spot on in that videos pack the most 'bang for the
buck' when it comes to training - maybe I should film more and write
less - at least they are easier to maintain into the future (dump the
old one and spend 15 minutes making a new one).
Keep up the good work Tomasz,
brian_z
--- In amibroker@xxxxxxxxxxxxxxx, "brian_z111" <brian_z111@xxx> wrote:
>
> Good day Ed,
>
> A very interesting background, and comments, especially since you
> don't post all that often.
>
> I spent 25 years in mining and referenced semi-trailer loads of
tech
> manuals in that time, including manuals for gas analyzers. They
were
> full of legal disclaimers and pre-amble and the only sections that
> were ever read, more than once, if at all, were the drawings and
the
> procedures - tech guys/engineers went straight to the drawings and
> specs (mud maps) and operators went straight to the 'how to get it
> going' procedures.
>
> In fact more often than not the mudmups and the 20 pages of
> procedures in the 1000 page manual were reprinted, bound and
> circulated and the book itself sat in the cupboard untouched.
>
> (Maybe I even read one of yours).
>
> 99% of operators never ever even picked up the manual.
> They relied on the 1% to write the 20 page version.
>
> People who do (the minority) are always vociferously criticized by
> those who don't (usually in inverse proportions).
>
> I think the motivation of AB owners is a lot higher than people in
> the workplace though (on average).
>
> I do empathise with Tomasz though - he must get sick of us
constantly
> dissecting his every move (sometimes people get a bit personal too
> which I think is very harmful). Also manuals are a thankless task
> because as soon as you finish them they are 'out of date'.
>
> Having written a couple of posts for the UKB I know how hard it is
to
> write - people have no idea of the work I put into them and how I
> agonize over the prose and the grammar (where will I put that
comma?)
>
> So in case I didn't make it clear before the only suggestion I am
> making to Tomasz is re the manual - people do expect AB to be
> accountable for the manual - I cringe when I go to it and see
> obsolete content that has been there for more than one update (Yes -
> TOC/Indexes/Searchability are crucial).
>
> However, while I talk about other 'training issues' I don't expect
> anything outside of the manual and I don't expect Tomasz to anyting
> else in that area (nice if he can but not realistic).
>
> The community support is excellent but it will never be perfect or
> perfectly organized and presented (unless we all do what Howard
does
> and sit down and write a formal presentation).
>
> I have tried to do walk through/plenty of pictures/examples etc at
> the UKB (that is what the UKB is for) don't know if I succeeded but
> there just isn't enough hours.
>
> So will I be seeing some posts from you at the UKB then?
>
> While I am here I would like to redress one misconception.
>
> I thought people were unfair, and lacked an understanding of
Tomasz,
> when they said they thought he couldn't write a good manual.
>
> IMO Tomasz would make a very good author, and not only for
technical
> manuals. His grammar is better than mine and when he wants to he
can
> turn out a nice piece of prose (we have to remember English isn't
his
> first language - how would we go writing in Polish?). He is also a
> creative person (an artist) and if he wanted to let loose on a book
I
> am sure he could do a good job.
>
> The only reason IMO that the manual is lagging the program is
because
> Tomasz doesn't have the time and also it is not as much fun as
> programming and he would rather be doing that (can't blame him for
> that).
>
> Re books:
>
> I always think that it is a great privilige, and I can't believe
how
> lucky I am, to be able to prop 20 years of
Howards/Kaufmans/Aronsons
> life, in condensed form, beside my bed and read them over and over
> until their experience blends with mine.
>
> Thanks for your comments - really enjoyed them.
>
> brian_z
>
>
>
>
>
> --- In amibroker@xxxxxxxxxxxxxxx, "Ed Hoopes" <reefbreak_sd@>
> wrote:
> >
> > I have been the author of about a dozen technical manuals for
> > industrial gas analyzers that used embedded computers/software to
> run
> > the instruments. Several were about 200 pages long.
> >
> > As such, I have heard all of the criticisms about inadequate
> manuals.
> > Too long, too short, too detailed, over simplified, too
theoretical
> etc.
> >
> > Here is my perspective:
> > 1. A "Quick Start" guide is good - patterned after many modern
> > electronic devices we buy today - tabloid size or larger -
> everything
> > on one page - lots of diagrams - fewer words - in the book as a
> > tear-out section.
> > 2. As a former 2nd year algebra teacher (before I got into
> instrument
> > design) - I think large numbers of errors are due to not knowing
the
> > rules of algebra as implemented in software. The users will take
> > their algebra errors and blame it on the software.
> > 3. Maybe something on 'structured walk thru' techniques (or what
> ever
> > is popular now) - to get users to fully think through everything
> > they are trying to code for.
> > 2. Example code of some relatively simple analysis - Years ago IBM
> > taught SQL(I think) using 'query by example', so maybe a chapter
on
> > 'Coding *.afl by example'
> > 4. Finally, EACH USER of your book will have different
> expectations -
> > you will not be able to make everyone happy, so in publishing your
> > guide, expect a steady stream of 'Don't buy Howard's book - It
> > didn't help me' kinds of comments.
> >
> > BTW - I bought QTS (2 copies - I gave one away) - I liked it.
> >
> > Ed Hoopes
> >
> > PS
> > Spending lots of time on the ToC and Index reduces the complaints,
> > especially if you can direct them to that area to locate their
> answer.
> > After a few complaints, they will start to look there rather
than
> post.
> >
> >
> >
> >
> >
> >
> >
> > --- In amibroker@xxxxxxxxxxxxxxx, "chorlton_c_hardy"
> > <chorlton-c-hardy@> wrote:
> > >
> > >
> > > Hello Howard,
> > >
> > > As a reader of your last book, I for one, look forward to
reading
> it.
> > >
> > > I have read your last book a number of times now and still keep
> > > learning new elements!!! Maybe I'm just a slow learner
though :-/
> > >
> > > Also, as a newbie to Amibroker & its langauge I'm very
surprised
> no
> > > one has considered writing one before, given the popularity of
> this
> > > excellent piece of software, so its good to hear that one is
now
> in
> > > the pipeline.....
> > >
> > > All the best,
> > >
> > > Chorlton
> > >
> > > --- In amibroker@xxxxxxxxxxxxxxx, "Howard B" <howardbandy@>
wrote:
> > > >
> > > > Hi Christopher --
> > > >
> > > > Since the book is so closely associated with AmiBroker, I'll
> use the
> > > > AmiBroker forum groups to announce the book.
> > > >
> > > > SO far, there are plans for only a printed version. But that
> might
> > > change.
> > > >
> > > > Thanks,
> > > > Howard
> > > >
> > > > On Feb 11, 2008 4:07 AM, Christopher <chrisjeal@> wrote:
> > > >
> > > > > Hi Howard,
> > > > > I would be interested in a book on how to use Amibroker
> > > correctly, how
> > > > > will you let people know when you have published the book?
> > > > >
> > > > > Have you thought of selling it as a pdf something like on
> > > clickbank?
> > > > > As you will have no costs up front and will sell as many as
> > > wanted no
> > > > > more and no less - also you could offer updated pages as
> needed.
> > > > > Just an Idea.
> > > > > Yours
> > > > > Chris
> > > > >
> > > > >
> > > > > --- In amibroker@xxxxxxxxxxxxxxx <amibroker%
> > > 40yahoogroups.com>, "Howard B"
> > > > > <howardbandy@> wrote:
> > > > > >
> > > > > > Greetings all --
> > > > > >
> > > > > > What a nice surprise, it looks like there is a new price
> point.
> > > I
> > > > > did not
> > > > > > think the market would bear so much. (Grin)
> > > > > >
> > > > > > " I WILL GET IT but I would pay $120.00 for the very
basics
> in
> > > afl in a
> > > > > > minute. "
> > > > > >
> > > > > > "Introduction to AmiBroker" is alive and well. I have
other
> > > > > projects that
> > > > > > are getting done along with writing it. Some days
> Introduction
> > > is
> > > > > on the
> > > > > > top of the list, other days it is not. But it will be
> published.
> > > > > >
> > > > > > It will be pretty much what its title says -- a book about
> > > > > AmiBroker. Since
> > > > > > AmiBroker is a trading system development platform, there
> will
> > > be
> > > > > discussion
> > > > > > of trading and trading systems. But, readers looking for
a
> book
> > > > > about the
> > > > > > design, testing, and validation of trading systems should
> look
> > > at
> > > > > > "Quantitative Trading Systems," which is already
available.
> The
> > > > > > Introduction book is a separate book, more about
AmiBroker,
> > > less about
> > > > > > trading systems, and at a more basic level. It is not a
new
> > > edition
> > > > > of QTS.
> > > > > >
> > > > > > Thanks for the suggestions about joint authorship. I have
> > > already
> > > > > explored
> > > > > > that.
> > > > > >
> > > > > > The author of a book gets very little compensation -- no
> matter
> > > how
> > > > > it is
> > > > > > published. Top end compensation for the author(s) -- if
> there
> > > are
> > > > > multiple
> > > > > > authors, they split this -- is usually about 10% of the
> retail
> > > price
> > > > > of the
> > > > > > book. A $40 book gives two authors $2.00 each per copy.
> > > > > Introduction to
> > > > > > AmiBroker might sell 2000 copies over two or three years.
> At
> > > the rate
> > > > > > Tomasz is expanding the capabilities of AmiBroker, it
would
> be
> > > unwise to
> > > > > > make too large a press run, and wise to plan on revised
> editions
> > > > > regularly.
> > > > > > There are several sections I have re-written already as
> > > AmiBroker
> > > > > changed,
> > > > > > and the first edition has not yet gone to press.
> > > > > >
> > > > > > There is little reward and a lot of difficulty
coordinating
> > > efforts.
> > > > > The
> > > > > > logistics of two people working from different locations
on
> a
> > > manuscript
> > > > > > several hundred pages long are very difficult.
> > > > > >
> > > > > > It is a one-person job.
> > > > > >
> > > > > > Thanks,
> > > > > > Howard
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Feb 8, 2008 12:25 PM, Ronald Davis <xokie7@> wrote:
> > > > > >
> > > > > > > Lloyd>>>I, also would like to see a presentation using
> first
> > > > > principles.
> > > > > > > My
> > > > > > >
> > > > > > > understanding is that Howard will be completing an
entry
> > > level book
> > > > > > > this spring as soon as he completes some obligations
this
> > > month.
> > > > > > >
> > > > > > > It might be a better book if Howard and Graham were to
> agree
> > > to
> > > > > JOINTLY
> > > > > > > write the book. The best and most understandable
> explanations
> > > that
> > > > > have
> > > > > > > been given to me have been those from Graham. Graham
> seems to
> > > have an
> > > > > > > outstanding ability to describe things in a very
> > > understandable
> > > > > way. Here
> > > > > > > is his description of SUM from the user manual. Ron D
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
>
======================================================================
> > > =====
> > > > > > > Sum adds up the last "n" number of bars. It sums
whatever
> you
> > > put
> > > > > into the
> > > > > > > first part of the sum formula.
> > > > > > >
> > > > > > > Cum(1) adds 1 to the previous value of Cum, so the
first
> bar
> > > is 1
> > > > > and it
> > > > > > > just keeps adding one to the last bar value of cum(1).
> > > > > > > You can use Cum to add anything, like how many times
you
> get
> > > > > rising days
> > > > > > > in
> > > > > > > the entire chart:
> > > > > > >
> > > > > > > Rise = C>O; //this gives results of 0 or 1
> > > > > > > TotalRise = Cum(Rise);
> > > > > > >
> > > > > > > You could limit this as well to time periods, or any
> other
> > > condition
> > > > > > > Example
> > > > > > > would be one for total rise days since 1995:
> > > > > > >
> > > > > > > RecentRise = C>O and Year()>=1995; //this gives results
> of 0
> > > or 1
> > > > > > > TotalRise = Cum(RecentRise);
> > > > > > >
> > > > > > > If you wanted to know how many rising days in the last
12
> > > bars you
> > > > > would
> > > > > > > use:
> > > > > > >
> > > > > > > LastRises = Sum(Rise,12);
> > > > > > >
> > > > > > >
> > >
> ===================================================================
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Thomas Ludwig" <Thomas.Ludwig@ <Thomas.Ludwig%
> > > 40gmx.de>>
> > > > > > > To: <amibroker@xxxxxxxxxxxxxxx <amibroker%
> > > 40yahoogroups.com><amibroker%40yahoogroups.com>>
> > > > > > > Sent: Friday, February 08, 2008 1:14 PM
> > > > > > > Subject: Re: [amibroker] Re: no amibroker book?
> > > > > > >
> > > > > > > > brian_z111 wrote:
> > > > > > > >
> > > > > > > >> However, I also agree with the others that we need a
> good
> > > AFL book
> > > > > > > >> and IMO Tomasz is the man to write it - yes, even if
> he
> > > has to stop
> > > > > > > >> development to do it - take a sabbatical and get out
> the
> > > feathered
> > > > > > > >> pen Tomasz
> > > > > > > >
> > > > > > > > Brian, I agree with Paul and vlanschot that TJ cannot
> > > afford to
> > > > > do this.
> > > > > > > > And quite frankly - no offense meant, TJ!!! - I'm not
> sure
> > > if
> > > > > he's the
> > > > > > > > right guy to do this. I'm afraid he's frequently
> thinking
> > > in quite
> > > > > > > > different categories than most of us who are non-
> > > programmers and
> > > > > > > > apparantly much more simple-minded ;-) He's often
made
> the
> > > statement
> > > > > > > > that every AB user should read the manual from the
> first to
> > > the last
> > > > > > > > page over and over again. Yes, true - but that
doesn't
> > > really
> > > > > help in
> > > > > > > > many situations.
> > > > > > > >
> > > > > > > > Examples? The description of Exrem and Exremspan -
> without
> > > hints
> > > > > from
> > > > > > > > other guys here in the mailing list (who are
obviously
> more
> > > > > intelligent
> > > > > > > > than I am) I would never have understood the whole
> purpose
> > > of these
> > > > > > > > functions and when to use them.
> > > > > > > > Another one: The description of Equity() - my
goodness,
> > > after
> > > > > all these
> > > > > > > > years I still have troubles at times to decide which
> flag I
> > > > > should use
> > > > > > > > and with which consequences.
> > > > > > > >
> > > > > > > > There are many other examples of functions available
in
> AB
> > > that
> > > > > may be
> > > > > > > > useful for me in specific situations - but I simply
> don't
> > > understand
> > > > > > > > and use them (like Varset). In the past I had very
> often the
> > > > > > > > impression - with a "normal" occupation, a wife and
two
> > > children who
> > > > > > > > sometimes felt neglected - that I'm the wrong target
> > > customer for AB
> > > > > > > > and TJ. But, well, over the years the moments of
> > > desperation have
> > > > > > > > become fewer thanks to a lot of pasting of infos from
> the
> > > list here
> > > > > > > > (like Graham has mentioned).
> > > > > > > >
> > > > > > > > Having said this, I think an AFL book is needed
written
> > > strictly
> > > > > from
> > > > > > > > the user's perspective. I think most of us non-
> programmers
> > > and
> > > > > > > > non-engineers are in need of "cooking recipes" that
> > > organize,
> > > > > structure
> > > > > > > > or arrange the vast multitude of possibilities
> available in
> > > AB in
> > > > > > > > order to facilitate everyday usage of this excellent
> > > application. A
> > > > > > > > nice example from the AB library as a starter would be
> > > > > > > > http://www.amibroker.com/library/detail.php?id=547
> > > > > > > >
> > > > > > > > Brian, Herman and you are doing a really marvelous
job
> for
> > > the
> > > > > UKB. But
> > > > > > > > perhaps some more of such "cooking recipes" should be
> > > included. It
> > > > > > > > would be great if more AB users could contribute them.
> > > > > > > >
> > > > > > > > Just my 2 cents ...
> > > > > > > >
> > > > > > > > Greetings,
> > > > > > > >
> > > > > > > > Thomas
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Please note that this group is for discussion between
> users
> > > only.
> > > > > > > >
> > > > > > > > To get support from AmiBroker please send an e-mail
> > > directly to
> > > > > > > > SUPPORT {at} amibroker.com
> > > > > > > >
> > > > > > > > For NEW RELEASE ANNOUNCEMENTS and other news always
> check
> > > DEVLOG:
> > > > > > > > http://www.amibroker.com/devlog/
> > > > > > > >
> > > > > > > > For other support material please check also:
> > > > > > > > http://www.amibroker.com/support.html
> > > > > > > >
> > > > > > > > Yahoo! Groups Links
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
For other support material please check also:
http://www.amibroker.com/support.html
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/amibroker/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:amibroker-digest@xxxxxxxxxxxxxxx
mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx
<*> To unsubscribe from this group, send an email to:
amibroker-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|