rising and falling triggers

[Brian Watson]

Dear colleagues,

In a spec on the types of blocks used in programming specs, I'm working on the

Trigger block. Three types are prohibited from use, and they are discussed in a

note. The three types are:

立ち上がり

立ち下がり

両方

With a little googling (and since this is just a note), I'm tempted to translate these

as 'rising', 'falling' and 'both'.

Does anyone have more accurate terminology?

Brian Watson
http://www.google.com/profiles/brian.watson
+1.604.395.4202 (home office), +1.425.246.7888 (cell), brian-momotaro (skype)

[Wolfgang Bechstein]

Brian Watson wrote:

> In a spec on the types of blocks used in programming specs, I'm working on
> the
> Trigger block. Three types are prohibited from use, and they are discussed
> in a
> note. The three types are:
>
> 立ち上がり
> 立ち下がり
> 両方
>
> With a little googling (and since this is just a note), I'm tempted to
> translate these as 'rising', 'falling' and 'both'.
>
> Does anyone have more accurate terminology?

I don't really know what "blocks used in programming specs" are, but in
terms of pulse signals used as triggers, 立ち上がり is usually called
leading edge and 立ち下がり trailing edge. Front edge and back edge are
also used. However, rising and falling aren't wrong either, I believe.
So I guess you're pretty near the solution already...

Wolfgang Bechstein

[Herman]

On 2/25/2012 15:40, Brian Watson wrote:
> Dear colleagues,
>
> In a spec on the types of blocks used in programming specs, I'm working
> on the
> Trigger block. Three types are prohibited from use, and they are
> discussed in a
> note. The three types are:
>
> 立ち上がり
> 立ち下がり
> 両方
>
> With a little googling (and since this is just a note), I'm tempted to
> translate these
> as 'rising', 'falling' and 'both'.
>

I believe the terms you are looking for are:

leading edge trigger
trailing edge trigger
dual edge trigger

Herman Kahn

[Brian Chandler]

Wolfgang Bechstein wrote:
> Brian Watson wrote:
>
> > In a spec on the types of blocks used in programming specs, I'm working on
> > the
> > Trigger block. Three types are prohibited from use, and they are discussed
> > in a
> > note. The three types are:
> >
> > 立ち上がり
> > 立ち下がり
> > 両方
> >
> > With a little googling (and since this is just a note), I'm tempted to
> > translate these as 'rising', 'falling' and 'both'.
> >
> > Does anyone have more accurate terminology?
>
> I don't really know what "blocks used in programming specs" are,

Makes no sense to me either, but I would guess the original uses the
Japanese ブロック. Whereas in English, "block" is an association of small
units, as in a "block of seats", in Japanese ブロック usually looks at
this from the viewpoint of dividing up something larger. So I expect
it just means the group of function (or whatever) that relate to
triggers.

> terms of pulse signals used as triggers, 立ち上がり is usually called
> leading edge and 立ち下がり trailing edge.

Yes and no. Sometimes trigger signals can have reverse polarity, in
which case the leading edge is a falling edge. So unless you know
exactly what is going on, I would render these literally as "rising",
"falling", "rising and falling". It is entirely possible that in the
great scheme of things you can specify any of

leading (either polarity)
trailing (either polarity)
rising (leading or trailing depending on polarity)
falling (leading or trailing depending on polarity)

and this particular part of the GSoT only allows the first two.

Brian Chandler

[Andrew Lardinois]

What programming language block is in question? For databases triggers are generally on update, on delete, and cascade.

--
You received this message because you are subscribed to the Honyaku Mailing list.
To unsubscribe from this group, send email to honyaku+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/honyaku?hl=en?hl=en

[Brian Watson]

2012/3/6 Andrew Lardinois <lard...@gmail.com>

What programming language block is in question? For databases triggers are generally on update, on delete, and cascade.

The file has been submitted to the client, and I've already forgotten what I ended up using. But these were definitely not database triggers.

Thanks,