Results for algorithm translation from Slovak to English

name of the hash algorithm
sha-0

name of the checksum algorithm
adler-32

final bessel filter constants and algorithm
step 3

@ label: listbox algorithm to use for the checksum
checksum

name of the checksum algorithm, cyclic redundancy check 32
modular sum 16-bit

algorithm 5 shall also run during night-time settlement .
algorithm 5 shall also run during night-time settlement .

design of bessel filter algorithm konštrukcia algoritmu besselovho filtra
fcnew = fc * (1 + delta)

design of bessel filter algorithm fc, e, k fc = fcnew
regulation taver [s]

if an algorithm is successful , the included payment orders will be settled ;
if an algorithm is successful , the included payment orders will be settled ;

if an algorithm fails , the included payment orders will remain in the queue .
if an algorithm fails , the included payment orders will remain in the queue .

final bessel filter constants and algorithm konečné konštanty a algoritmus besselovho filtra
final bessel filter constants and algorithm yi = …

requests for reordering or revocation of a payment order shall be queued until the algorithm is complete .
requests for reordering or revocation of a payment order shall be queued until the algorithm is complete .

if the payment order concerned is settled while the algorithm is running , any request to reorder or revoke shall be rejected .
if the payment order concerned is settled while the algorithm is running , any request to reorder or revoke shall be rejected .

pole 4.008: algoritmus kompresie odtieňov šedej (gca – gray-scale compression algorithm)
field 4.008: greyscale compression algorithm (gca)

payment orders that are included in an algorithm , as referred to in appendix i , may not be revoked during the period that the algorithm is running .
payment orders that are included in an algorithm , as referred to in appendix i , may not be revoked during the period that the algorithm is running .

while included in a running algorithm , a payment order shall not be reordered ( change of the position in a queue ) or revoked .
while included in a running algorithm , a payment order shall not be reordered ( change of the position in a queue ) or revoked .

algorithm to be used for the compression of grayscale images in type-4, type-7 and type-13 to type-15 records.
algorithm to be used for the compression of greyscale images in type-4, type-7 and type-13 to type-15 records.

to optimise the settlement of highly urgent ancillary system transactions on participants » subaccounts , a special algorithm ( algorithm 5 ) shall be used .
to optimise the settlement of highly urgent ancillary system transactions on participants » sub-accounts , a special algorithm ( algorithm 5 ) shall be used .

by means of algorithm 4 , settlement procedure 5 ( as defined in chapter 2.8.1 of the udfs ) shall be available for the settlement of payment instructions of ancillary systems .
by means of algorithm 4 , settlement procedure 5 ( as defined in chapter 2.8.1 of the udfs ) shall be available for the settlement of payment instructions of ancillary systems .

( a ) under algorithm 1 (' all-or-nothing ') the ecb shall , both for each relationship in respect of which a bilateral limit has been set and also for the total sum of relationships for which a multilateral limit has been set : ( i ) calculate the overall liquidity position of each target2 participant 's pm account by establishing whether the aggregate of all outgoing and incoming payment orders pending in the queue is negative or positive and , if it is negative , check whether it exceeds that participant 's available liquidity ( the overall liquidity position shall constitute the « total liquidity position ') ;
( a ) under algorithm 1 (' all-or-nothing ') the ecb shall , both for each relationship in respect of which a bilateral limit has been set and also for the total sum of relationships for which a multilateral limit has been set : ( i ) calculate the overall liquidity position of each target2 participant 's pm account by establishing whether the aggregate of all outgoing and incoming payment orders pending in the queue is negative or positive and , if it is negative , check whether it exceeds that participant 's available liquidity ( the overall liquidity position shall constitute the « total liquidity position ') ;