PEXPJX–PEXPJ4 Sets exponential acceleration/deceleration time constant sequentially in manual feed.
[Setting value] 0 to 4000
[Unit] msec
NOTE If 0 is set then cutting feed and common data (PRM529) is used.
0605 PFLJGX
0606 PFLJGY
0607 PFLJGZ
0608 PFLJG4
PFLJGX–PFLJG4 Sets exponential acceleration/ deceleration rate sequentially in manual feed.
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
NOTE If 0 is set then all axes common data (PRM548) is used.
0609 In–position width for cutting feed for X–axis
0610 In–position width for cutting feed for Y–axis
0611 In–position width for cutting feed for Z–axis
0612 In–position width for cutting feed for 4th axis
[Data unit] Detection unit
[Data range] 0 to 32767
[Description] These parameters specify the in–position width for cutting feed, for the cutting feed and rapid traverse separate in–position check function.
[Data range]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
84
NOTE These parameters are effective when bit 4 of parameter 0045 (CCINP) is set to 1.
0613 TPFDT POWER OFF
TPFDT Time constants of spindle and Z–axis acceleration/deceleration in the tapping in the rigid mode (Exponential/linear type is selected by TPSUP.) The threading accuracy is affected when the time constant is either too long or too short.
[Data type] Word
[Setting value] 0 to 4000
[Unit] msec
[Standard setting] 200 to 150 � When VALT (parameter No. 37) =1
Set the time constant when cutting the thread of
standard lead = TPFBS (parameter No. 626)
TPSMX (parameter No. 617) The inclination of the acceleration/deceleration of the spindle is defined by this. This function adjusts the actual time constant so as to maintain the inclination of the acceleration/dcelartion of the spindle even when any lead thread is cut under any conditions.

NOTE Becauses the time constant is produced by proportional calculation even in the case of exponential–type aceleration/deceleration, there will be a small increase in error compared to linear–type acceleration/deceleration.
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
85
� When VALT (parameter No. 37) =0
1. In case of exponential–type acceleration/deceleration
Time constat
F
2. In case of linear–type acceleration/deceleration
Set the time taken to reach the lower limit speed (parameter No. 527 FEDMX) of the cutting feed.
Time constat
FEDMX
0614 TPFFL POWER OFF
TPFFL Lower speed limit (valid only when TPSUP=0) at exponential acceleration/deceleration of the spindle and Z–axis in the rigid tapping. When this is increased, tact time is reduced, but the threading accuracy is affected.
[Data type] Word
[Setting value] 6 to 15000
[Unit] mm/min
[Standard setting] 30 to 10
0615 TPLPG POWER OFF
TPLPG Spindle and Z–axis position control loop gain in the parameter in rigid tapping. This has a large influence upon the threading accuracy. Make fine adjustment to obtain theoptimum value by performing the cutting test and matching with the loop gain multiplier.
[Data type] Word
[Setting value] 1 to 9999
[Unit] 0.01 msec–1
[Standard set value]1500 to 3000
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
86
NOTE To change the loop gain for each gear, reset the value of this parameter to 0 and set the loop gain for each gear in TPLGL (No. 0669), TPLGM (No. 0670) and TPLGH (No. 0671). If this parameter is not 0, the loop gain for each gear becomes invalid and the value set in this parameter is taken as a loop gain common to all gears.
0616 LPGM9 POWER OFF
LPGM9 Loop gain multiplier of the spindle in the rigid tapping for the high speed range. This has a large influence upon the thread accuracy. Make fine adjustment to obtain the optimum value by performing the cutting test and matching with the loop gain.
[Data type] Word
[Setting value] 1 to 32767
Set value= 2048�E/L�@�1000 E = Speed command voltage at 1000 rpm L = Spindle rotation angle per spindle motor rotation @ = Detection unit Calculation example:
When the configuration is as shown in the following figure:
Main axis
SPINDLE
MOTOR
P.C
POsition coder
1:1:2
E = 1.667 [V] (motor of 6000 rpm at 10 [V]) L=360° (Spindle is rotated one turn by one spindle motor rotation.) @ = La/4096
=720°/4096 =0.17587°
La = 720° Spindle must make two rotations =360° * 2 for rotating the position coder one turn.) 4096 = Detection pulse per position coder rotation.
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
87
� Gear ratio between the spindle and the position coder 1 : 1 . . . 0.08789 deg 1 : 2 . . . 0.17578 deg 1 : 4 . . . 0.35156 deg 1 : 8 . . . 0.70313 deg
Therefore, the loop gain multiplier = 2048 � 1.667/360 � 0.17578 � 1000 = 1667
NOTE Donot miss to set the gear ratio parameter (No. 0028) between the detection unit based on this parameter.
0617 TPSMX POWER OFF
TPSMX Maximum allowable speed of the spindle in the rigid tapping.
[Data type] Word
[Setting value] (for spindle and position coder gear ratio) Gear ratio Setting range
1 : 1 0 to 7400 1 : 2 0 to 9999 1 : 4 0 to 9999 1 : 8 0 to 9999
[Unit] PRM
[Standard setting] 3600
0618 TPIPZ
TPIPZ Z–axis in–position width in the rigid tapping
[Data type] Word
[Setting value] 1 to 32767
[Unit] Detection unit
[Standard setting] 20
0619 INP9
INP9 Spindle in–position width in the rigid tapping When this is too much increased, the threading accuracy is affected.
[Data type] Word
[Setting value] 0 to 32767
[Unit] Detection unit
[Standard setting] 20
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
88
0620 TPERZ
TPERZ Limit value of position deviation during movement of Z axis in the rigid tapping mode
[Data type] Word
[Setting value] 0 to 32767
[Unit] Detection unit
When a one–tenth resolution detector is used, the unit becomes ten times the detection unit.
0621 TPER9
TPER9 Limit value of position deviation during movement of the spindle in the rigid mode tapping
[Data type] Word
[Setting value] 1 to 32767 Set value = S � 360/60 � 1/G � 1/@ �100 � 1.5
S: Maximum spindle speed to perform the rigid tapping (Value of parameter No. 0617)
G: Loop gain in the rigid mode tapping axis (Value of parameter No. 0615)
@:Detection unit for spindle and position coder gear ratio
Gear ratio Detection unit 1 : 1 ......... 0.8789 deg 1 : 2 ......... 0.17578 deg 1 : 4 ......... 0.35156 deg 1 : 8 ......... 0.70313 deg
Calculation example: S = 3600 G = 3000 @ = 0.17578
(Gear ratio between spindle and position coder 1:2)
TPER9 = (3600�360)/60�1/3000�1/0.17578�100�1.5 = 6144
0622 TPESZ
TPESZ Limit value of position deviation during stop of Z axis in the rigid mode tapping
[Data type] Word
[Setting value] 0 to 32767
[Unit] Detection unit
[Standard setting] 500
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
89
0623 TPES9
TPES9 Limit value of position deviation during stop of the spindle in the rigid mode tapping
[Data type] Word
[Setting value] 0 to 32767
[Unit] Detection unit
[Standard setting] 500
0624 LGM9M POWER OFF
LGM9M Spindle loop gain multiplier in the rigid mode tapping for middle gear. (Set when two–stage or more gears are used).
[Data type] Word
[Setting value] 1 to 32767 Set value = 2048 � E/L � @ � 1000
E = Speed command voltage at 1000 rpm L = Spindle rotation angle per spindle motor rotation @ = Detection unit
Calculation example: When the configuration is as shown in the following figure:
2 : 1 : 2
Main axisSPINDLE
MOTOR P.C
Position coder
E = 1.667 [V] (motor of 6000 rpm at 10 [V])
L = 720° (Spindle is rotated one turn by one spindle motor rotation.)
@ = La/4096 = 720°/4096 = 0.17578°
La = 720° (Spindle must make two rotations=360° � 2 for rotating the position coder one turn.) 4096 = Detection pulse per position coder rotation
Loop gain multiplier = 2048�1.667�360�0.17578�1000
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
90
0625 LGM9H POWER OFF
LGM9H Spindle loop gain multiplier for high speed gear in parameter is the rigid tapping. (Used for 3–stage gear).
[Data type] Word
[Setting value] 1 to 32767
NOTE Refer to parameter No. 0624 for calculation formula.
Send speed for rigid mode tapping standard lead constant
TPFBS: Send speed for standard read constant for rigid mode tapping.
0626 TPPBS POWER OFF
TPFBS Feedrate for standard lead constant for rigid mode tapping
[Data type] Word
[Setting value] 6 to 15000
[Unit] mm/min
NOTE VALT (parameter No.37)=1 is valid. Outside the above setting range, use FML10=1 of parameter No.49. Also, even when setting unit is 1/10 the unit is the same.
0627 ERR9
ERR9 Spindle position deviation value in the rigid tapping. (Used for diagnosis)
[Data type] Word
[Unit] Detection unit
0628 IPR9
IPR9 Spindle distribution amount in the rigid tapping. (Used for diagnosis)
[Data type] Word
[Unit] Detection unit
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
91
0651 PEFDTX
0652 PEFDTY
0653 PEFDTZ
0654 PEFDT4
PEFDTX – 4 Time constants of exponential acceleration/ deceleration of PMC axis cutting feed for each axis.
[Setting value] 0 to 4000
[Unit] msec
NOTE When 0 is set, the data for NC (PRM No. 529) is used.
0657 PEFLX
0658 PEFLY
0659 PEFLZ
0660 PEFL4
PEAFLX – 4 Lower limit speeds (FL) at exponential acceleration/deceleration of PMC axis cutting feed for each axis.
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
NOTE When 0 is set, the cutting FL speed for NC (PRM No. 530) is used.
0663 GRPLW
GRPLW Set the number of teeth of the 1st stage gear in the spindle when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1. When the position coder is provided in the spindle, set the same value in GRPLW, GRPMD and GRPHI.
[Data range]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
92
0664 GRPMD
GRPMD Set the number of teeth of the 2nd stage gear in the spindle when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1.
0665 GRPHI
GRPHI Set the number of teeth of the 3rd stage gear in the spindle when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1.
0666 GRQLW
GRQLW Set the number of teeth of the 1st stage gear in the position coder when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1. When the position coder is provided in the spindle, set the same value in GRQLW, GRQMD and GRQHI. When the spindle coder is built in the spindle motor, a position coder of 2048 p/rev is available. At this time, set the number of teeth by the value double the actual number. (For converting to 4096 p/rev) This is the same for GRQMD and GRQHI.
0667 GRQMD
GRQMD Set the number of teeth of the 2nd stage gear in the position coder when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
93
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1
0668 GRQHI
GRQHI Set the number of teeth of the 3rd stage gear in the position coder when the gear ratio is optional in the rigid tapping mode.
[Data type] Word
[Setting value] 1 to 32767
NOTE Valid when VALPC (parameter No.63) = 1.
0669 TPLGL POWER OFF
TPLGL Loop gain for position control of the spindle and Z–axis of each gear in the rigid tapping mode. Set the position control loop gain of the 1st stage gear.
[Data type] Word
[Setting value] 1 to 9999
[Unit] 0.01 msec–1
0670 TRLGM POWER OFF
TRLGM Loop gain for position control of the spindle and Z–axis of each gear in the rigid tapping mode. Set the position control loop gain of the 2nd stage gear.
[Data type] Word
[Setting value] 1 to 9999
[Unit] 0.01 msec–1
0671 TPLGH POWER OFF
TPLGH Loop gain for position control of the spindle and Z–axis of each gear in the rigid tapping mode. Set the position control loop gain of the 3rd stage gear.
[Data type] Word
[Setting value] 1 to 9999
[Unit] 0.01 msec–1
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
94
0672 FL speed of reference point return by PMC axis control
[Data type] Word
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
FL speed of reference point return by PMC axis control is set. When “0” is set, parameter 534 is used for FL spped of PMC axis control.
0683 Rotation speed of normal direction control
[Data type] Word
[Data unit] 1 deg/min
[Data range] 6 to 15000
Rotation speed for inserted rotary axis motion at the corner is set when using normal direction control.
0684 Declaration end speed of error detect function
[Data type] Word
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
Declaration end speed of error detect function is set. When command speed becomes less than the setting value, the next block starts.
0685 F0 speed of PMC axis control with using independent rapid override
[Data type] Word
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
F0 speed of PMC axis control is set when using override independent of CNC axis control.
NOTE This parameter is effective when setting both parameter 078#7 (EAXOVE) and 078#6 (RDRNE) are set to “1”.
[Data range]
[Data unit]
[Data range]
[Data unit]
[Data range]
[Data unit]ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
95
0686 Backlash compensation value for rapid traverse for X–axis
0687 Backlash compensation value for rapid traverse for Y–axis
0688 Backlash compensation value for rapid traverse for Z–axis
0689 Backlash compensation value for rapid traverse for 4th axis
Setting system IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
[Data range] 0 to 2550
[Description] These parameters specify the backlash compensation value for rapid traverse for each axis.
0692 Time constant of rigid tapping for low gear
[Data type] Word
[Data unit] 1 msec
[Data range] 0 to 4000
Time constant of acc/dec in rigid tapping for middle gear is set. When linear acc/dec (parameter 254 = 1) and parameter 037#6 (VALT) = 1 is selected, this parameter indicates the required time from spindle speed 0 to parameter 695. Actual time constant varys proportionally to the actual spindle speed. When parameter 037#6 (VALT) is set to 0, this parameter indicates real time constant for all tapping with middle gear.
NOTE 1 This parameter is effective only when parameter 077#1
(CT3G) is set to “1”. 2 Parameter 0613 should be set the time constant for high
gear .
0693 Time constant of rigid tapping for middle gear
[Data type] Word
[Data unit] 1 msec
[Data range] 0 to 4000
Time constant of acc/dec in rigid tapping for middle gear is set. When linear acc/dec (parameter 254 = 1) and parameter 037#6 (VALT) = 1 is selected, this parameter indicates the required time from spindle speed 0 to parameter 695. Actual time constant varys proportionally to the actual spindle speed. When parameter 037#6 (VALT) is set to 0, this parameter indicates real time constant for all tapping with middle gear.
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
96
NOTE 1 This parameter is effective only when parameter 077#1
(CT3G) is set to “1”. 2 Parameter 0613 should be set the time constant for high
gear.
0694 Maximum spindle speed of rigid tapping for low gear
[Data type] Word
[Data unit] rpm
Gear ratio between spindle and position coder Data range
1 :1 1:2 1:4 1:8
0 to 7400 0 to 9999 0 to 9999 0 to 9999
Maximun spindle speed of rigid tapping for low gear is set.
NOTE 1 This parameter is effective only when both parameter
077#1 (CT3G) and 037#6 (VALT) are set to “1”. 2 Maximum spindle speed of rigid tapping for high gear
should be set in parameter 617.
0695 Maximum spindle speed of rigid tapping for middle gear
[Data type] Word
[Data unit] rpm
Gear ratio between spindle and position coder Data range
1 :1 1:2 1:4 1:8
0 to 7400 0 to 9999 0 to 9999 0 to 9999
Maximun spindle speed of rigid tapping for middle gear is set.
NOTE 1 This parameter is effective only when both parameter
077#1 (CT3G) and 037#6 (VALT )are set to “1”. 2 Maximum spindle speed of rigid tapping for high gear
should be set in parameter 617.
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
97
0696 Instantaneous difference of servo lags between tapping axis and spindle
[Data type] Word
[Data unit] %
Instantaneous difference of servo lags between tapping axis and spindle is indicated as DGN data.
0697 Maximum difference of servo lags between tapping axis and spindle
[Data type] Word
[Data unit] %
Maximum difference of servo lags between tapping axis and spindle is indicated as DGN data.
0698 Maximum feedrate per revolution by PMC axis control
[Data type] Word
Setting unit Data unit Data range
Setting unit Data unit IS–A, IS–B IS–C
Millimeter machine 1 [mm/min] 6 to 15000 6 to 12000
Inch machine 0.1 [inch/min] 6 to 6000 6 to 4800
Rotation axis 1 [deg/min] 6 to 15000 6 to 12000
Maximum feedrate per revolution by PMC axis control is set.
0699 Multiplier for handle feed
[Data type] Word
[Data range] 0t ot �1000
The multiplier of handle feed with both handle motion select signals MP1 and MP2 on is set. When minus value is specified, the actual motion is opposite of handle direction.
NOTE When “0” is specified, parameter 121 becomes effective instead of this parameter .
[Data range]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
98
0700 LT1X1
0701 LT1Y1
0702 LT1Z1
0703 LT141
0704 LT1X2
0705 LT1Y2
0706 LT1Z2
0707 LT142
LT1��
nth top in square zone (see figure). axis
2
1
ÎÎÎÎÎ ÎÎÎÎÎ ÎÎÎÎÎ
Set stroke limit mentioned above.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
[Setting value] 0 to �99999999
Set with the distance from the reference point. In the case of diameter designation, set with the diameter designation value. The outside of the boundary set with the parameter is set as the inhibited region. Normally, set at the max. stroke of the machine. When the axis enters the inhibited region, overtravel alarm is indicated. A margin should be provided with respect to the stroke to cope with the fluctuation in the detecting operation. As a rule, in the case of metric designation, multiply the rapid traverse by a factor of 1/5 and set it as the margin.
Example) Rapid traverse 10 m/min. 10 � 1/5 = 2 mm The actual position of the machine slightly differs from the position stored in the CNC unit after the power is turned on, emergency stop is reset, or servo alarm is reset. Therefore, before starting operation, be sure to return the axes to reference point. Otherwise, overtravel detecting position deviates by the value corresponding to the above–described deviation in the position. When the parameters are set as follows, the stroke limit becomes infinite. LT1�1<LT1�2
Axis name
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
99
Example) LT1Z1 = –1 and LT1Z2 = 1 the Z axis stroke becomes infinite.
NOTE 1 For the axis whose stroke is infinite, the incremental
command can be specified. If the absolute command is specified, the absolute register may overflow and it is not operated normally.
2 These parameters cannot be set for the rotary axis.
0708 PRSX
0709 PRSY
0710 PRSZ
0711 PRS4
PRSX, PRSY, PRSZ, PRS4 These set the coordinate values of the reference point of the X, Y, Z and 4th axes when automatic coordinate system setting is conducted, respectively.
[Setting range] 0 to �99999999
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
0712 PECINTX POWER OFF
0713 PECINTY
0714 PECINTZ
0715 PECINT4
PECINTX, PECINTY, PECINTZ, PECINT4 Pitch error compensation interval for each axis.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting range] 8000 to 99999999 4000 to 99999999
NOTE If zero is set, no compensation is done.
[Data unit]
[Data unit]ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
100
0735 REF2X
0736 REF2Y
0737 REF2Z
0738 REF24
REF2X, REF2Y, REF2Z, REF24 Distance frim the reference point to the 2nd reference point for X, Y, Z, and 4th axes, respectively.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting range] 0 to �99999999
0739 ABSXP POWER OFF
0740 ABSYP
0741 ABSZP
0742 ABS4P
ABSXP, ABSYP, ABSZP, ABS4P Counter data at the reference point when the absolute pulse ABSYP, coder is used. These parameters are automatically set when the tool has returned to the reference point. So it is not necessary to set values to these parameters.
0743 LT2X1
0744 LT2Y1
0745 LT2Z1
0746 LT241
0747 LT2X2
0748 LT2Y2
0749 LT2Z2
0750 LT242
LT2X1–LT242 Check stroke limit using these parameters, not parameter Nos. 0700 to 0707 when EXLM2 (G129.6) signal is ON.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
[Data unit]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
101
[Data range] 0 to �99999999
NOTE Valid only when parameter No. 915LM2=1.
0751 EXOFS1
0752 EXOFS2
0753 EXOFS3
0754 EXOFS4
EXOFS1 to 4 External work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th–axis in sequence.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �7999
NOTE This parameter sets the zero–point position of work coordinate system (G54 to G59). The work zero–point offset amount is different for every work coordinate system, but this parameter sets the offset amount common to all work coordinate systems. Normally, machine–side input (external data input) is used for automatic setting.
0755 ZOF1S1
0756 ZOF1S2
0757 ZOF1S3
0758 ZOF1S4
ZOFISI to 4 1st work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence. (G54)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �99999999
Normally, data are inputted from the work coordinate system setting screen.
[Data unit]
[Data unit]ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
102
0759 ZOF2S1
0760 ZOF2S2
0761 ZOF2S3
0762 ZOF2S4
ZOF2S1 to 4 2nd work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence. (G55)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �99999999
Normally, data are inputted from the work coordinate system setting screen.
0763 ZOF3S1
0764 ZOF3S2
0765 ZOF3S3
0766 ZOF3S4
ZOF3S1–4 3rd work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence.
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
Normally, data are inputted from the work coordinate system setting screen.
0767 ZOF4S1
0768 ZOF4S2
0769 ZOF4S3
0770 ZOF4S4
ZOF4S1 to 4 4th work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence. (G57)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �99999999
Normally, data are input from the work coordinate system setting screen.
[Data unit]
[Data unit]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
103
0771 ZOF5S1
0772 ZOF5S2
0773 ZOF5S3
0774 ZOF5S4
ZOF5S1 to 4 5th work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence. (G58)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �99999999
Normally, data are input from the work coordinate system setting screen.
0775 ZOF6S1
0776 ZOF6S2
0777 ZOF6S3
0778 ZOF6S4
ZOF6S1 to 4 6th work zero–point offset amount of X–axis, Y–axis, Z–axis and 4th axis in sequence. (G59)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
Rotation axis [deg] 0.01 0.001 0.0001
[Setting value] 0 to �99999999
Normally, data are input from the work coordinate system setting screen.
0779 PARTAL
PARTAL No. of machined parts in total
[Setting value] 0 to 99999999
0797 Lock for displaying part program No. 9000 to 9999
[Data type] 2 word
[Data range] 0 to 99999999
A number is set to prohibit displaying part programs which program number is from 9000 to 9999. This parameter is effective only when 010#4 (PRG9) is set to “1”. Parameter PRG9 can not be turned to “0” unless parameter 798 is coincident with the parameter.
The actual setting value is not displayed.
[Data unit]
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
104
0798 Key for displaying part program No. 9000 to 9999
[Data type] 2 word
[Data range] 0 to 99999999
Parameter PRG9 can be turned to “0” if the same number as parameter 797 is set in this parameter.
The actual setting value is not displayed too.
0799 ABS9
ABS9 Spindle distribution cumulative value for the rigid tapping. (Used for diagnosis)
[Data type] 2–word
[Unit] Detection unit
0815 PRSTIX
0816 PRSTIY
0817 PRSTIZ
0818 PRSTI4
PRSTIX – PRSTI8 Coordinate values of the reference point in automatic coordinate system setting. (Input is in inch and PRM No.63 bit 1 PRSTIN=1)
Setting unit IS–A IS–B IS–C
Millimeter machine [mm] 0.01 0.001 0.0001
Inch machine [inch] 0.001 0.0001 0.00001
[Setting value] 0 to �99999999
0832 Limit angle of inserting rotary axis motion for normal direction control
[Data type] 2 word
[Data unit] 0.001 deg
[Data range] 1 to 99999999
When the rotation angle is less than the specified value, no rotary axis motion of normal direction control is inserted.
0833 Limit motion for inserting rotary axis motion for normal direction control
[Data type] 2 word
[Data unit] input increment
[Data range] 1 to 99999999
When tha command motion is less than the specified value, no rotary axis motion of normal direction control is inserted.
[Data unit]
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
105
N2
N1 N3
motion
diameter
N3 N2
N1
In case of linear motion, If the motion of N2 is less than the specified value, no rotary axis motion is in- serted at the corner of N1/ N2.
In case of circle motion, if the diameter of N2 is less than the specified value, no rotary axis motion is in- serted at the corner of N1/ N2 and along the circle N2.
0838 Minimum grinding wheel diameter for a grinding wheel diameter check
[Data unit] 0.001 (mm) for metric input, or 0.0001 (inches) for inch input
[Data range] 0 to 999999
[Description] Specifies the minimum grinding wheel diameter to be used in a grinding wheel diameter check.
NOTE Bit 3 of F165 (GWLF) becomes 1 when the specified compensation amount is less than the minimum grinding wheel diameter.
0860 Movement of rotary axis per one revolution
[Data type] 2 word
[Data unit] input increment
[Data range] 1000 to 10000000
Movement of rotary axis per one revolution is set for roll–over function.
0876 Tolerance of circle radius between start point and end point
[Data type] 2 word
[Data unit] input increment
[Data range] 0 to 99999999
The tolerance of circle radius between start point and end point is set. When the difference of radius between start point and end point exceeds the specified value, alarm 20 will appear.
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
106
0957 Maximum spindle lag of rigid tapping for low gear
0958 Maximum spindle lag of rigid tapping for middle gear
0959 Maximum spindle lag of rigid tapping for high gear
[Data type] 2 word
[Data unit] detection unit of spindle
[Data range] 0 to 32767
Maximum spindle lag of rigid tapping for low, middle and high gear is set respectively.
NOTE These parameter are effective only when parameter 388#6 (CHKERC) is set to “1”.
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
107
Setting pitch error compensation
Pitch error compensation points are located at equal intervals, specified for each axis. Pitch error compensation is performed at the midpoint of each compensation interval. (See the following figure.)
+3
+2
+1
–1
–2
Compensation value
Reference position
Compensation point number34 35 36<PHONE_NUMBER>
Compensation interval
Compensation point number 30 31 32 33 34 35 36 37
Set compensation value –2 +3 –1 –1 +1 +2 –1 –3
If the compensation interval is set to 0, pitch error compensation is not performed for that axis. The minimum interval between pitch error compensation points is limited to the following value:
Minimum pitch error compensation interval = Maximum rapid traverse rate/1875
Example: When the maximum rapid traverse rate is 15000 mm/min, the minimum interval between pitch error compensation points is 8 mm.
0712 Compensation interval for X–axis pitch error compensation
0713 Compensation interval for Y–axis pitch error compensation
0714 Compensation interval for Z–axis pitch error compensation
0715 Compensation interval for 4th–axis pitch error compensation
[Data unit] Output units
[Data range] 8000 to 99999999 (metric output) 4000 to 99999999 (inch output)
[Description] These parameters are used to set the interval between pitch error compensation points for each axis.
Setting the pitch error compensation interval
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
108
Up to 128 pitch error compensation points can be set. Among them, specify the pitch error compensation point that corresponds to the reference position, as the pitch error compensation origin. In the following example, the pitch error compensation number corresponding to the reference position is set to 33:
Reference position
Compensation point34 35 36<PHONE_NUMBER>
1000 Pitch error compensation origin for the X–axis
to
4000 Pitch error compensation origin for the 4th axis
[Data range] 0 to 128
[Description] These parameters are used to set the number of the pitch error compensation origin for each axis.
Set the pitch error compensation for each compensation interval. The pitch error compensation can be set within a range of 0 to �7. The actual compensation values are obtained by multiplying the set values by a magnification specified with a parameter.
Example:
� Machine stroke : –400 mm to +800 mm
� Pitch error compensation origin : 40
� Pitch error compensation interval : 50 mm
� Farthest compensation number in the positive direction = (compensation origin number) + (positive stroke/compensation interval) = 40 + 800/50= 56
� Farthest compensation number in the negative direction = (compensation origin number) – (negative stroke/compensation interval) + 1 = 40 – 400/50 + 1 = 33
Machine coordinate (mm)
Compensation point number
–400 –350 –100 –50 0 50 100 750 800
33 39 40 41 42 56
Setting the pitch error compensation origin
Setting the pitch error compensation
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
109
The compensation corresponding to each compensation point number is output at the midpoint of the corresponding interval. The following is an example:
Number 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Compensation +2 +1 +1 –2 0 –1 0 –1 +2 +1 0 –1 –1 –2 0 +1 +2
Pitch error compensation (absolute value)
–400 –300 –200 –100 0 100 200 300 400 (mm) –1
–2
–3
–4
+4
+3
+2
+1
4039383736353433<PHONE_NUMBER>434241 49
Compensation point number
Machine coordinate
�001 Pitch error compensation value of No.0 of �–th axis
to
�128 Pitch error compensation value of No.127 of �–th axis
[Data range] 0 to �7
[Description] Set the pitch error compensation value of No.0 to 127 of �–th axis
#7 0011
#6 #5 #4 #3 #2 #1 PML2
#0 PML1
POWER OFF
PML1, PML2 Set the magnification of pitch error compensation as below table.
#1 PML2
#0 PML1 Magnification
0 0 �1
0 1 �2
1 0 �4
1 1 �8
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
110
For a rotation axis, pitch error compensation of rotation axis type is performed, such that any compensation points in the negative direction are ignored. The result obtained by adding one to the result of dividing the angle corresponding to a single revolution (360000) by the pitch error compensation interval is set as the number of compensation points for a rotation axis.
Machine coordinate
Compensation point number
0° 360°
0 1 2 n–1 n
(+)(–)
Reference position
n: Result obtained by dividing the angle corresponding to a single revolution (360000) by the pitch error compensation interval
Set 0 as the pitch error compensation origin. Set an identical value for the pitch error compensation for both compensation points 0 and n.
Example: When the pitch error compensation interval is set to 6°.
Parameter Set value
Pitch error compensation origin 0
Pitch error compensation interval 6000
In this case, set compensation values as follows:
(� indicates the axis number.)
Parameter (pitch error
compensation value)
Set value of parameter
�001 Compensation value between –6° and 0° (Compensation value between 354° and 360°)
�002 Compensation value between 0° and 6°
�003 Compensation value between 6° and 12°
� �
�060 Compensation value between 348° and 354°
�061 Compensation value between 354° and 360° (Compensation value between –6° and 0°)
NOTE 1 Set a compensation interval such that 360000 can be
divided exactly by that value, without a remainder. Otherwise, compensation will not be performed normally.
2 The sum of the compensation values for a single revolution must be 0.
Setting pitch error compensation for a rotation axis
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
111
Parameters related to serial interface spindle
The following parameters are not described in detail. The standard settings listed in the tables need be modified for some machine systems.
Sub–spindle parameters when the spindle switching function is provided
First spindle
Second spindle
Description Standard setting
6140 6141 6142 6143 6144 6145 6146 6147 6148 6149
6320 6321 6322 6323 6324 6325 6326 6327 6328 6329
Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter
00000000 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
6150 6151 6152 6153 6154 6155 6156 6157 6158 6159
6330 6331 6332 6333 6334 6335 6336 6337 6338 6339
Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter
00000000 Model–dependent Model–dependent Model–dependent
00000000 00000000 00000000 00000000 00000000 00000000
6160 6161 6162 6163 6164 6165 6166 6167 6168 6169
6340 6341 6342 6343 6344 6345 6346 6347 6348 6349
Maximum motor speed Speed arrival detection level Speed detection level Speed zero detection level Torque limit value Load detection level 1 Output limit pattern Output limit value Position coder method orientation stop position
Model–dependent 150 30 75 50 83 0
100 0 0
6170 6171 6172 6173 6174 6175 6176 6177 6178 6179
6350 6351 6352 6353 6354 6355 6356 6357 6358 6359
Normal velocity loop proportional gain (HIGH) Normal velocity loop proportional gain (LOW) Velocity loop proportional gain during orientation (HIGH) Velocity loop proportional gain during orientation (LOW) Velocity loop proportional gain in servo mode (HIGH) Velocity loop proportional gain in servo mode (LOW) Normal velocity loop integral gain Velocity loop integral gain during orientation Velocity loop integral gain in servo mode
10 10 10 10 10 10 10 10 10 0
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
112
Sub–spindle parameters when the spindle switching function is provided
First spindle
Standard settingDescriptionSecond spindle
6180 6181 6182 6183 6184 6185 6186 6187 6188 6189
6360 6361 6362 6363 6364 6365 6366 6367 6368 6369
Gear ratio (HIGH) Gear ratio (LOW) Position gain during orientation (HIGH) Position gain during orientation (LOW) Position gain change ratio when orientation is completed Position gain in servo mode (HIGH) Position gain in servo mode (LOW) Grid shift amount in servo mode
100 100
1000 1000 100
1000 1000
0 0 0
6190 6191 6192 6193 6194 6195 6196 6197 6198 6199
6370 6371 6372 6373 6374 6375 6376 6377 6378 6379
Orientation completion signal detection level Motor velocity limit value during orientation Orientation stop position shift amount MS signal constant MS signal gain adjustment Regenerative power limit Delay time prior motor power shut–off Acceleration/deceleration time setting
10 33 0 – 0
Model–dependent 20 10 0 0
6200 6201 6202 6203 6204 6205 6206 6207 6208 6209
6380 6381 6382 6383 6384 6385 6386 6387 6388 6389
Motor voltage during normal rotation Motor voltage during orientation Motor voltage in servo mode Position gain change ratio when returning to the origin in the servo mode Feed forward factor Velocity loop feed forward factor
Model–dependent Model–dependent Model–dependent
100 0 0 0 0 0 0
6210 6211 6212 6213 6214 6215 6216 6217 6218 6219
6390 6391 6392 6393 6394 6395 6396 6397 6398 6399
0 0 0 0 0 0 0 0 0 0
6220 6221 6222 6223 6224 6225 6226 6227 6228 6229
6400 6401 6402 6403 6404 6405 6406 6407 6408 6409
Base velocity of the motor output specification Limit value for the motor output specification Base speed Magnetic flux weakening start velocity Current loop proportional gain during normal operation Current loop integral gain during normal operation Zero point of current loop integral gain Current loop proportional gain velocity factor Current conversion constant Secondary current factor for exciting current
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
113
Sub–spindle parameters when the spindle switching function is provided
First spindle
Standard settingDescriptionSecond spindle
6230 6231 6232 6233 6234 6235 6236 6237 6238 6239
6410 6411 6412 6413 6414 6415 6416 6417 6418 6419
Current expectation constant Slip constant High–speed rotation slip compensation constant Compensation constant of voltage applied to motor in the dead zone Electromotive force compensation constant Electromotive force phase compensation constant Electromotive force compensation velocity factor Time constant for changing the torque Load meter displayed value for maximum output Maximum output zero point
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
5 Model–dependent Model–dependent
6240 6241
6242 6243 6244 6245 6246 6247
6420 6421
6422 6423 6424 6425 6426 6427
Secondary current factor during rigid tapping Constant for compensating for the phase of the electromotive force at deceleration Time constant of the speed detection filter
Time constant of voltage filter for electromotive force compensation
Model–dependent Model–dependent
0 0 0 0 0 0
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
114
Sub–spindle parameters for low–speed operation when the spindle switching function is provided and the output switching function is provided for the sub–spindle
First spindle
Second spindle
Description Standard setting
6248 6249
6428 6429
Motor voltage during normal rotation Motor voltage in the servo mode
Model–dependent Model–dependent
6250 6251 6252 6253 6254 6255 6256 6257 6258 6259
6430 6431 6432 6433 6434 6435 6436 6437 6438 6439
Base speed of the motor output specifications Limit value for the motor output specifications Base speed Magnetic flux weakening start velocity Current loop proportional gain during normal operation Current loop integral gain during normal operation Zero point of the current loop integral gain Velocity factor of the current loop proportional gain Current conversion constant Secondary current factor for activating current
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
6260 6261 6262 6263 6264 6265 6266 6267 6268 6269
6440 6441 6442 6443 6444 6445 6446 6447 6448 6449
Current expectation constant Slip constant High–speed rotation slip compensation constant Compensation constant for voltage applied to motor in the dead zone Electromotive force compensation constant Electromotive force phase compensation constant Velocity factor of the electromotive force compensation Time constant for changing the torque Maximum output zero point Secondary current factor during rigid tapping
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
6270 6271 6272 6273 6274 6275 6276 6277 6278 6279
6450 6451 6452 6453 6454 6455 6456 6457 6458 6459
Voltage compensation factor during deceleration Regenerative power limit Time constant of voltage filter for electromotive force compensation Motor model code
Model–dependent Model–dependent
0 Model–dependent
0 0 0 0 0 0
6280 6281 6282 6283 6284 6285 6286 6287 6288 6289
6460 6461 6462 6463 6464 6465 6466 6467 6468 6469
0 0 0 0 0 0 0 0 0 0
6290 6291 6292 6293 6294 6295 6296 6297 6298 6299
6470 6471 6472 6473 6474 6475 6476 6477 6478 6479
0 0 0 0 0 0 0 0 0 0
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
115
Sub–spindle parameters for low–speed operation when the spindle switching function is provided and the output switching function is provided for the sub–spindle
First spindle
Standard settingDescriptionSecond spindle
6300 6301 6302 6303 6304 6305 6306 6307 6308 6309
6480 6481 6482 6483 6484 6485 6486 6487 6488 6489
0 0 0 0 0 0 0 0 0 0
6310 6311 6312 6313 6314 6315
6490 6491 6492 6493 6494 6495
Overload current alarm detection level (for low speed characteristic) Overload current alarm detection time constant Overload current alarm detection level (for high speed characteristic) Compensation for current detection offset
0 0
Model–dependent Model–dependent Model–dependent
0
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
116
Parameters for standard motors (parameters for high–speed operation when the output switching function is provided)
First spindle
Second spindle
Description Standard setting
6500 6501 6502 6503 6504 6505 6506 6507 6508 6509
6640 6641 6642 6643 6644 6645 6646 6647 6648 6649
Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter
00000000 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
6510 6511 6512 6513 6514 6515 6516 6517 6518 6519
6650 6651 6652 6653 6654 6655 6656 6657 6658 6659
Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter Bit parameter
00000000 Model–dependent Model–dependent Model–dependent
00000000 00000000 00000000 00000000 00000000 00000000
6520 6521 6522 6523 6524 6525 6526 6527 6528 6529
6660 6661 6662 6663 6664 6665 6666 6667 6668 6669
Maximum motor speed Maximum speed when the Cs axis is controlled Speed arrival detection level Speed detection level Speed zero detection level Torque limit value Load detection level 1 Load detection level 2 Output limit pattern Output limit value
Model–dependent 100 150 30 75 50 83 95 0
100
6530 6531 6532 6533 6534 6535 6536 6537 6538 6539
6670 6671 6672 6673 6674 6675 6676 6677 6678 6679
Soft start/stop time Position coder method orientation stop position Acc./dec. time constant when the spindle synchronization is controlled Arrival level for the spindle synchronization speed Shift amount when the spindle phase synchronization is controlled Spindle phase synchronization compensation data Feed forward factor Velocity loop feed forward factor
0 0 0
100 0
10 0 0 0 0
6540 6541 6542 6543 6544 6545 6546 6547 6548 6549
6680 6681 6682 6683 6684 6685 6686 6687 6688 6689
Normal velocity loop proportional gain (HIGH) Normal velocity loop proportional gain (LOW) Velocity loop proportional gain during orientation (HIGH) Velocity loop proportional gain during orientation (LOW) Velocity loop proportional gain in servo mode (HIGH) Velocity loop proportional gain in servo mode (LOW) Velocity loop proportional gain when the Cs axis is controlled (HIGH) Velocity loop proportional gain when the Cs axis is controlled (LOW) Normal velocity loop integral gain (HIGH) Normal velocity loop integral gain (LOW)
10 10 10 10 10 10 30 30 10 10
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
117
Parameters for standard motors (parameters for high–speed operation when the output switching function is provided)
First spindle
Standard settingDescriptionSecond spindle
6550 6551 6552 6553 6554 6555 6556 6557 6558 6559
6690 6691 6692 6693 6694 6695 6696 6697 6698 6699
Velocity loop integral gain during orientation (HIGH) Velocity loop integral gain during orientation (LOW) Velocity loop integral gain in servo mode (HIGH) Velocity loop integral gain in servo mode (LOW) Velocity loop integral gain when the Cs axis is controlled (HIGH) Velocity loop integral gain when the Cs axis is controlled (LOW) Gear ratio (HIGH) Gear ratio (MEDIUM HIGH) Gear ratio (MEDIUM LOW) Gear ratio (LOW)
10 10 10 10 50 50
100 100 100 100
6560 6561 6562 6563 6564 6565 6566 6567 6568 6569
6700 6701 6702 6703 6704 6705 6706 6707 6708 6709
Position gain during orientation (HIGH) Position gain during orientation (MEDIUM HIGH) Position gain during orientation (MEDIUM LOW) Position gain during orientation (LOW) Position gain change ratio when orientation is completed Position gain in servo mode (HIGH) Position gain in servo mode (MEDIUM HIGH) Position gain in servo mode (MEDIUM LOW) Position gain in servo mode (LOW) Position gain when the Cs axis is controlled (HIGH)
1000 1000 1000 1000 100
1000 1000 1000 1000 3000
6570 6571 6572 6573 6574
6575 6576 6577 6578 6579
6710 6711 6712 6713 6714
6715 6716 6717 6718 6719
Position gain when the Cs axis is controlled (MEDIUM HIGH) Position gain when the Cs axis is controlled (MEDIUM LOW) Position gain when the Cs axis is controlled (LOW) Grid shift amount in servo mode Reference position return speed in Cs contouring control mode or servo mode Orientation completion signal detection level Motor velocity limit value during orientation Orientation stop position shift amount MS signal constant MS signal gain adjustment
3000 3000 3000
0 0
10 33 0 – 0
6580 6581 6582 6583 6584 6585 6586 6587 6588 6589
6720 6721 6722 6723 6724 6725 6726 6727 6728 6729
Regenerative power limit Delay time prior motor power shut–off Acceleration/deceleration time setting Motor voltage during normal rotation Motor voltage during orientation Motor voltage in servo mode/synchronous control Motor voltage when the Cs axis is controlled Over–speed detection level Excessive velocity deviation detection level when the motor is constrained Excessive velocity deviation detection level when the motor is rotated
Model–dependent 20 10
Model–dependent Model–dependent Model–dependent Model–dependent
115 75
200
6590 6591 6592 6593 6594 6595 6596 6597 6598 6599
6730 6731 6732 6733 6734 6735 6736 6737 6738 6739
Overload detection level Position gain change ratio when returning to the origin in the servo mode Position gain change ratio when returning to the origin in Cs axis control Acceleration presumed constant Disturbance torque compensation constant Speed meter output voltage adjustment value Load meter output voltage adjustment value Spindle velocity feedback gain Maximum speed at which position coder signal can be detected Delay time for energizing the motor
90 100 100
0 0 0 0 0 0 0
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
118
Parameters for standard motors (parameters for high–speed operation when the output switching function is provided)
First spindle
Standard settingDescriptionSecond spindle
6600 6601 6602 6603 6604 6605 6606 6607 6608 6609
6740 6741 6742 6743 6744 6745 6746 6747 6748 6749
Base velocity of the motor output specification Limit value for the motor output specification Base speed Magnetic flux weakening start velocity Current loop proportional gain during normal operation Current loop proportional gain at the Cs contour control Current loop integral gain during normal operation Current loop integral gain at the Cs contour control Zero point of current loop integral gain Current loop proportional gain velocity factor
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
6610 6611 6612 6613 6614 6615 6616 6617 6618 6619
6750 6751 6752 6753 6754 6755 6756 6757 6758 6759
Current conversion constant Secondary current factor for exciting current Current expectation constant Slip constant High–speed rotation slip compensation constant Compensation constant of voltage applied to motor in the dead zone Electromotive force compensation constant Electromotive force phase compensation constant Electromotive force compensation velocity factor Time constant of voltage filter for electromotive force compensation
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
0
6620 6621 6622 6623 6624 6625 6626 6627 6628 6629
6760 6761 6762 6763 6764 6765 6766 6767 6768 6769
Dead zone compensation data Time constant for changing the torque Velocity filter Overload detection time setting
Timer during automatic running Velocity command during automatic running Load meter displayed value for maximum output Maximum output zero point Secondary current factor during rigid tapping
Model–dependent 5 0
30 0
100 1000
Model–dependent Model–dependent Model–dependent
6630
6631 6632 6633 6634 6635
6770
6771 6772 6773 6774 6775
Constant for compensating for the phase of the electromotive force at deceleration Time constant of the speed detection filter at the Cs contour control Conversion constant of the phase–V current Motor model code
Grid shift amount when the C axis is controlled
Model–dependent
0 0
Model–dependent 0 0
ww w.
cn cc
en ter
.co m
B–62580EN/01 4. DESCRIPTION OF PARAMETERS
119
Parameters for low–speed operation when the output switching function is provided
First spindle
Second spindle
Description Standard setting
6900 6901 6902 6903 6904 6905 6906 6907 6908 6909
6940 6941 6942 6943 6944 6945 6946 6947 6948 6949
Motor voltage during normal rotation Motor voltage in the servo mode Base speed of the motor output specifications Limit value for the motor output specifications Base speed Magnetic flux weakening start velocity Current loop proportional gain during normal operation Current loop integral gain during normal operation Zero point of current loop integral gain Velocity factor of current loop proportional gain
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
6910 6911 6912 6913 6914 6915 6916 6917 6918 6919
6950 6951 6952 6953 6954 6955 6956 6957 6958 6959
Current conversion constant Secondary current factor for excitation current Current expectation constant Slip constant Compensation constant for high–speed rotation slip Compensation constant for voltage applied to motor in the dead zone Electromotive force compensation constant Phase compensation constant for electromotive force Compensation velocity factor for electromotive force
Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent Model–dependent
0
6920 6921 6922 6923 6924 6925
6926 6927 6928 6929
6960 6961 6962 6963 6964 6965
6966 6967 6968 6969
Time constant for changing the torque Maximum output zero point Secondary current factor in rigid tapping Hysteresis of the speed detection signal (SDT) output Constant for compensating for the phase of the electromotive force at deceleration Velocity loop integral gain when the Cs axis is controlled (HIGH) Velocity loop integral gain when the Cs axis is controlled (LOW) Conversion constant of the phase–V current Time constant of voltage filter for eletromotive force compensation
0 Model–dependent Model–dependent Model–dependent
0 Model–dependent
0
0 0 0
6930 6931 6932 6933 6934 6935 6936 6937 6938 6939
6970 6971 6972 6973 6974 6975 6976 6977 6978 6979
Regenerative power limit
Overload current alarm detection level (for low speed characteristic) Overload current alarm detection time constant Overload current alarm detection level (for high speed characteristic)
Delay timer at ON of electromagnetic contactor in unit
Model–dependent 0
Model–dependent Model–dependent Model–dependent
– 0 0 0 0
ww w.
cn cc
en ter
.co m
B–62580EN/014.  DESCRIPTION OF PARAMETERS
121
No. Contents
No. #1#1#2#3#4#5#6#7
8�32
8�33
8�34
8�35
8�36
8�37
8�38
8�39
8�40 POWER OFF Current loop gain (PK1)
8�41 POWER OFF Current loop gain (PK2)
8�42 POWER OFF Current loop gain (PK3)
8�43 Velocity (integral) loop gain (PK1V)
8�44 Velocity (proportional) loop gain (PK2V)
8�45 Incomplete integral coefficient (PK3V)
8�46 Velocity loop gain (PK4V)
8�47 Velocity control observer parameter (POA1)
8�48 Improvement of velocity control backlash compensation (BLCMP)
8�49 Maximum width of dual position feedback (DPFMAX)
8�50 Velocity control observer parameter (POK1)
8�51 Velocity control observer parameter (POK2)
8�52
8�53 Compensation for current non–operating area (PPMAX)
8�54 Compensation for current non–operating area (PDDP)
8�55 Compensation for current non–operating area (PHYST)
8�56 Back electromotive force compensation (EMFCMP)
8�57 Current phase control (PVPA)
8�58 Current phase control (PALPH)
8�59 Back electromotive force compensation (EMFBAS)
8�60 POWER OFF Torque limit (TQLIM)
8�61 Back electromotive force compensation (EMFLMT)
8�62 Overload protection coefficient (OVC1)
8�63 Overload protection coefficient (OVC2)
8�64 TG alarm level (TGALMLV)
8�65 Overload protection coefficient (OVCLMT)
8�66 PK2VAUX
8�67 Torque command filter (TCFIL)
ww w.
cn cc
en ter
.co m
B–62580EN/014. DESCRIPTION OF PARAMETERS
122
No. Contents
No. #1#1#2#3#4#5#6#7
8�68 Feed–forward coefficient (FALPH)
8�69 Feed–forward coefficient of velocity loop (VFFLT)
8�70 Backlash compensation acceleration parameter (ERBLN)
8�71 Backlash compensation acceleration parameter (PBLCT)
8�72
8�73
8�74 Velocity–dependent current loop gain (AALPH)
8�75
8�76 1msec acceleration feedback gain (WKAC)
8�77 Overshoot preventive counter (OSCTP)
8�78 Numerator of dual position feedback conversion coefficient (PDPCH)
8�79 Denominator of dual position feedback conversion coefficient (PDPCL)
8�80 Time constant of dual position feedback (DPFTC)
8�81 Zero width of dual position feedback (DPFZW)
8�82 Backlash acceleration end amount (BLEND)
8�83 Brake control hold time of gravity axis (MOFCT)
8�84 POWER OFF Numerator of DMR when the flexibly feed gear is used (SDMR1)
8�85 POWER OFF Denominator of DMR when the flexibly feed gear is used (SDMR2)
8�86 Rated current parameter (RTCURR)
8�87 Torque offset of new type backlash acceleration (TCPRLD)
8�88 Mechanical speed feedback gain (MCNFB)
8�89 Base pulse in backslash acceleration (BLBSL)
8�90
8�91
8�92
8�93
8�94
8�95
8�96
8�97
8�98 Phase progress compensation coefficient in deceleration (DEPVPL)
8�99 ww
w. cn
cc en
ter .co
m
IndexB–62580EN/01
i–1
�F� Function parameters, 1
�P� Parameter description, 20
Parameter related to coordinate systems, 4
Parameters related to acceleration/deceleration control, 6
Parameters related to canned cycles, 13
Parameters related to control in the normal direction, 15
Parameters related to controlled axes and the increment system, 3
Parameters related to custom macro, 16
Parameters related to DI/DO, 8
Parameters related to manual handle feed, 17
Parameters related to pitch error compensation, 11
Parameters related to PMC axis control, 18
Parameters related to programming, 11
Parameters related to rigid tapping, 14
Parameters related to servo motors, 7
Parameters related to spindle control, 12
Parameters related to the CRT/MDI, display, and editing, 9
Parameters related to the display of operation time and number of parts, 17
Parameters related to the feedrate, 5
Parameters related to the PMC, 19
Parameters related to the reader/punch interface, 2
Parameters related to the software operator’s panel, 17
Parameters related to the stroke limit, 4
Parameters related to the surface grinding machine, 18
Parameters related to tool compensation, 13
Parameters related to unidirectional positioning, 15
�S� Setting parameter, 2, 22
ww w.
cn cc
en ter
.co m
R ev
is io
n R
ec or
d
FA N
U C
S er
ie s
0– M
D /0
–G S
D P
A R
A M
E T
E R
M A
N U
A L
(B –6
25 80
E N
)
01 M
ar .,
’9 7
E di
tio n
D at
e C
on te
nt s
E di
tio n
D at
e C
on te
nt s
ww w.
cn cc
en ter
.co m


Hatton, Emmilane Jane “Lena”
| Birth Name | Hatton, Emmilane Jane “Lena” |
| Gender | female |
| Age at Death | 73 years, 3 months, 15 days |
Narrative
ASHCROFT - Lena - 24 Nov, 1951, at Liverpool, widow of the late E. T. H. Ashcroft, & dear mother of Enid, Joyce (Mrs.R.Rowe), Audry (Mrs.J.Renehan), & loving grandmother of Jennifer & Elizabeth, aged 73 years.
FUNERAL - ASHCROFT - The Rels & Friends of the family of the late LENA ASHCROFT of 93 Northumberland St, Liverpool, are kindly invited to attend her Funeral, to leave St Luke's Church, Liverpool; This Monday, after a service at 2.45pm, for Church of England Cemetery, Liverpool.
Events
| Event | Date | Place | Description | Sources |
|---|---|---|---|---|
| Birth | 1878-08-09 | Liverpool NSW | ||
|
|
||||
| Death | 1951-11-24 | Liverpool NSW (73yrs) | ||
|
|
||||
| Burial | 1951-11-27 | Church of England Cemetery, Liverpool. | ||
|
|
Families
Family of Ashcroft, Edward Thomas Harrington “Ted” and Hatton, Emmilane Jane “Lena” |
|||||||||||||||||
| Married | Husband | Ashcroft, Edward Thomas Harrington “Ted” ( * 1877-12-31 + 1950-12-08 ) | |||||||||||||||
|
|||||||||||||||||
| Children |
| Name | Birth Date | Death Date |
|---|---|---|
| Ashcroft, Lorna Doreen | 1901-04-10 | 1904-07-10 |
| Ashcroft, Enid Amy | 1907-03-11 | 1995-04-14 |
| Ashcroft, [Living] | ||
| Ashcroft, Audrey Beatrice “Beatty” | 1911-11-12 | 2006-01-21 |
| Type | Value | Notes | Sources |
|---|---|---|---|
| _UID | 3260341ECCFBDA1195228CA643707552F948 |
Attributes
| Type | Value | Notes | Sources |
|---|---|---|---|
| _UID | 3160341ECCFBDA1195228CA643707552F838 |
Pedigree
-
- Hatton, Emmilane Jane "Lena"


ABOUT
GOODIES
RULES
FAQ's
CONTACT US
ABOUT
GOODIES
RULES
WELCOME TO
HACKTOBERFEST
GDSC-128 X HACKTOBERFEST
CONTRIBUTE
JOIN US


Spark Streaming Custom Receivers
Spark Streaming can receive streaming data from any arbitrary data source beyond the ones for which it has built-in support (that is, beyond Kafka, Kinesis, files, sockets, etc.). This requires the developer to implement a receiver that is customized for receiving data from the concerned data source. This guide walks through the process of implementing a custom receiver and using it in a Spark Streaming application. Note that custom receivers can be implemented in Scala or Java.
Implementing a Custom Receiver
This starts with implementing a Receiver (Scala doc, Java doc). A custom receiver must extend this abstract class by implementing two methods
onStart()
: Things to do to start receiving data.onStop()
: Things to do to stop receiving data.
Both onStart()
and onStop()
must not block indefinitely. Typically, onStart()
would start the threads
that are responsible for receiving the data, and onStop()
would ensure that these threads receiving the data
are stopped. The receiving threads can also use isStopped()
, a Receiver
method, to check whether they
should stop receiving data.
Once the data is received, that data can be stored inside Spark
by calling store(data)
, which is a method provided by the Receiver class.
There are a number of flavors of store()
which allow one to store the received data
record-at-a-time or as whole collection of objects / serialized bytes. Note that the flavor of
store()
used to implement a receiver affects its reliability and fault-tolerance semantics.
This is discussed later in more detail.
Any exception in the receiving threads should be caught and handled properly to avoid silent
failures of the receiver. restart(<exception>)
will restart the receiver by
asynchronously calling onStop()
and then calling onStart()
after a delay.
stop(<exception>)
will call onStop()
and terminate the receiver. Also, reportError(<error>)
reports an error message to the driver (visible in the logs and UI) without stopping / restarting
the receiver.
The following is a custom receiver that receives a stream of text over a socket. It treats ‘\n’ delimited lines in the text stream as records and stores them with Spark. If the receiving thread has any error connecting or receiving, the receiver is restarted to make another attempt to connect.
Using the custom receiver in a Spark Streaming application
The custom receiver can be used in a Spark Streaming application by using
streamingContext.receiverStream(<instance of custom receiver>)
. This will create
an input DStream using data received by the instance of custom receiver, as shown below:
The full source code is in the example CustomReceiver.scala.
The full source code is in the example JavaCustomReceiver.java.
Receiver Reliability
As discussed in brief in the Spark Streaming Programming Guide, there are two kinds of receivers based on their reliability and fault-tolerance semantics.
- Reliable Receiver - For reliable sources that allow sent data to be acknowledged, a reliable receiver correctly acknowledges to the source that the data has been received and stored in Spark reliably (that is, replicated successfully). Usually, implementing this receiver involves careful consideration of the semantics of source acknowledgements.
- Unreliable Receiver - An unreliable receiver does not send acknowledgement to a source. This can be used for sources that do not support acknowledgement, or even for reliable sources when one does not want or need to go into the complexity of acknowledgement.
To implement a reliable receiver, you have to use store(multiple-records)
to store data.
This flavor of store
is a blocking call which returns only after all the given records have
been stored inside Spark. If the receiver’s configured storage level uses replication
(enabled by default), then this call returns after replication has completed.
Thus it ensures that the data is reliably stored, and the receiver can now acknowledge the
source appropriately. This ensures that no data is lost when the receiver fails in the middle
of replicating data – the buffered data will not be acknowledged and hence will be later resent
by the source.
An unreliable receiver does not have to implement any of this logic. It can simply receive
records from the source and insert them one-at-a-time using store(single-record)
. While it does
not get the reliability guarantees of store(multiple-records)
, it has the following advantages:
- The system takes care of chunking that data into appropriate sized blocks (look for block interval in the Spark Streaming Programming Guide).
- The system takes care of controlling the receiving rates if the rate limits have been specified.
- Because of these two, unreliable receivers are simpler to implement than reliable receivers.
The following table summarizes the characteristics of both types of receivers
| Receiver Type | Characteristics |
|---|---|
| Unreliable Receivers |
Simple to implement. System takes care of block generation and rate control. No fault-tolerance guarantees, can lose data on receiver failure. |
| Reliable Receivers |
Strong fault-tolerance guarantees, can ensure zero data loss. Block generation and rate control to be handled by the receiver implementation. Implementation complexity depends on the acknowledgement mechanisms of the source. |


Object | +--HopObject
Defined in HopObject.js
See:
| SUMMARY: Constructor | Properties | Methods | DETAIL: Constructor | Properties | Methods |
| Constructor Summary | |
HopObject()
Constructor for HopObject objects, providing the building blocks of the Helma framework. |
| Properties Summary | |
Number |
_id
The unique id of the HopObject. |
HopObject |
_parent
The parent collection containing this HopObject. |
| Methods Summary | |
Boolean
|
add(<HopObject> subnode)
Attaches a HopObject as an additional subnode. |
Boolean
|
addAt(<Number> position,<HopObject> subnode)
Attaches an additional subnode at the given index. |
Object
|
cache()
Cache object providing space for arbitrary run-time data. |
void
|
clearCache()
Clears this HopObject's cache property. |
Number
|
contains(<HopObject> obj)
Determines if a HopObject contains a certain subnode. |
Number
|
count()
Get the number of subnodes attached to this HopObject. |
void
|
forEach(<Function> callback)
Iterates over each child node of the HopObject. |
HopObject
|
get(<String> id)
Retrieves a property or a subnode of a HopObject. |
HopObject
|
getById(<Number> id,<String> proto)
Retrieves the specified HopObject. |
HopObject
|
getChildElement(<String> name)
Optional handler to override the default URL path resolution. |
Array
|
getOrderedView(<String> name)
Returns a collection including all subnodes of a HopObject ordered according to the properties listed in the string passed as argument. |
helma.framework.repository.Resource
|
getResource(<String> resourceName)
Returns a helma.framework.repository.Resource object defined for the prototype. |
Array
|
getResources(<String> resourceName)
Returns an Array of helma.framework.repository.Resource objects defined for the prototype. |
String
|
href(<String> action)
Returns the absoulte URL path of a HopObject relative to the application's root. |
void
|
href_macro(param, action)
macro returns the url for any hopobject |
void
|
id_macro()
macro returns the id of a HopObject |
Number
|
indexOf(<HopObject> obj)
Determines if a HopObject contains a certain subnode. |
void
|
invalidate(childId)
Marks a HopObject as invalid so that it is fetched again from the database. |
Array
|
list()
Returns an array including all subnodes of a HopObject. |
void
|
loop_macro(param, collection)
generic macro that loops over the childobjects and renders a specified skin for each of them |
void
|
onInit()
If a HopObject prototype defines a function named onInit(), it will be called on each HopObject that is fetched from embedded or relational database. |
void
|
onPersist()
If a HopObject prototype defines a function named onPersist(), it will be called on each HopObject immediately before it is stored to embedded or relational database. |
void
|
onRequest()
If defined, the onRequest() function is called on the object specified by the request path just before the action is invoked. |
void
|
onUnhandledMacro(<String> name)
If a HopObject prototype defines a function named onUnhandledMacro(), it will be called when a macro is rendered on the HopObject that can't be mapped to a macro function or property of the HopObject. |
void
|
persist()
Stores a transient HopObject and all HopObjects reachable from it to database. |
void
|
prefetchChildren(<Number> startIndex, <Number> length)
Manually retrieving a particular set of subnodes. |
void
|
remove()
Deletes a HopObject from the database. |
void
|
removeChild(<HopObject> child)
Notifies a parent object that a child object has been removed. |
void
|
renderSkin(<String> skin, <Object> params)
Renders a skin of a HopObject and writes the result to the output buffer. |
String
|
renderSkinAsString(<String> skin, <Object> params)
Renders a skin of a HopObject and returns the result as string. |
void
|
setParent(<HopObject> subnode)
Assigns a HopObject as parent to a subnode. |
Number
|
size()
Get the number of subnodes attached to this HopObject. |
void
|
size_macro(<Object> param, <String> name)
Render the number of child nodes of the HopObject. |
void
|
skin_macro(param, name)
macro rendering a skin or displaying its source (param.as == "source") |
void
|
switch_macro(param)
this macro renders a text depending on the value of a given property |
void
|
update()
Refetches updateable Subnode-Collections from the database. |
| Constructor Detail |
HopObject()
| Properties Detail |
Number _id
HopObject _parent
| Method Detail |
Boolean add(<HopObject> subnode)
subnode
- as HopObject to add to this node.
Boolean addAt(<Number> position,<HopObject> subnode)
position
- as Number, the index position where the subnode is to be inserted.
subnode
- as HopObject to add to this node.
Object cache()
var obj = root.get(0); obj.cache.message = "This is a temporary message."
void clearCache()
Number contains(<HopObject> obj)
obj
- as HopObject, the node to look for
Number count()
res.write(root.count()); 5
void forEach(<Function> callback)
callback
- The callback function to be called for each child node. On every call the first argument of this function is set to the current value of the counter variable i
.
HopObject get(<String> id)
root.get(0); HopObject author root.get(1); HopObject story root.get("date"); Wed Oct 18 02:01:41 GMT+01:00 1971 root.get("title"); The Nudist On The Late Shift root.get("1"); HopObject author
id
- as String or Number
HopObject getById(<Number> id,<String> proto)
//get the child with id 17 var child = root.getById(17); writeln(child._id); 17 //get the child at index 17 of the HopObject's children-collection child = root.get(17); writeln(child._id); 42 //get the child with the name "17" (_children.accessname = name) of the HopObject child = root.get("17"); writeln(child._id); 69 writeln(child.name); 17 //get the persistent HopObject with prototype "Page" and id 127 var page = HopObject.getById(127, "Page"); writeln(page._id); 127 //get the persistent HopObject with prototype "Page" and id 127 var page = Page.getById(127); writeln(page._id); 127
id
- as Number
proto
- as String, the name of the prototype
HopObject getChildElement(<String> name)
function getChildElement(name) { if (name == 'transient') { return new HopObject(); } else { return this.get(name); } }
name
- as String, the name of the child element in the requested URL path
Array getOrderedView(<String> name)
var orderedByDate = hobj.getOrderedView("createtime desc, name"); for (var i in orderedByDate) { doSomething(); } // other syntax examples: var orderedByName = hobj.getOrderedView("name"); var collectionByName = hobj.collection.getOrderedView("name");
name
- as String, the property names to sort by
helma.framework.repository.Resource getResource(<String> resourceName)
root.getResource("main.skin"); /usr/local/helma-apps/myApp/repository1/HopObject/main.skin root.getResource("type.properties"); /usr/local/helma-apps/myApp/repository3/Root/type.properties root.getResource("Functions.js"); /usr/local/helma-apps/myApp/repository17/Root/Functions.js
resourceName
- as String, the name of the requested resource
Array getResources(<String> resourceName)
resourceName
- as String, the name of the requested resource
String href(<String> action)
var obj = root.get(0); res.write('');  res.write('');
action
- as String, optional part to be attached to the URL of this HopObject
void href_macro(param, action)
void id_macro()
Number indexOf(<HopObject> obj)
var obj = root.get("myObject"); res.write(root.indexOf(obj)); 23 obj = root.get("blobject"); res.write(root.indexOf(obj)); -1
obj
- as HopObject, the node to look for
void invalidate(childId)
var obj = this.get(0); obj.invalidate();
Array list()
var objectList = root.list(); for (var i=0; i < objectList.length; i++){ var myObject = objectList[i]; res.writeln(myObject.created); } Wed Oct 18 02:01:41 GMT+01:00 1971 Fri Nov 03 13:25:15 GMT+01:00 2000 Mon May 29 07:43:09 GMT+01:00 1999
var amount = root.size(); for (var i=0; i < amount; i++){ var myObject = root.get(i); res.writeln(myObject.created); } Wed Oct 18 02:01:41 GMT+01:00 1971 Fri Nov 03 13:25:15 GMT+01:00 2000 Mon May 29 07:43:09 GMT+01:00 1999
void loop_macro(param, collection)
Object
- providing the following properties: skin: the skin to render for each item (required) collection: the collection containing the items limit: max. number of items per page (req.data.page determines the page number) sort: property name to use for sorting order: sort order (either "asc" or "desc") itemPrefix: text to prepend to each items skin render itemSuffix: text to append to each items skin render
void onInit()
void onPersist()
void onRequest()
void onUnhandledMacro(<String> name)
name
- as String, the name of the unhandled macro
void persist()
var hobj = new HopObject(); hobj.foo = new HopObject(); res.debug(hobj.persist()); 2 res.debug(hobj.foo._id) 3
void prefetchChildren(<Number> startIndex, <Number> length)
res.writeln(root.length); 53874 root.prefetchChildren(0, 3); for (var i=0; i<3; i++) res.writeln(i + ": " + root.get(i)); HopObject 1 HopObject 5 HopObject 4
startIndex
- as Number
length
- as Number
void remove()
res.write(parent.size()); 24 var child = parent.get(5); child.remove(); parent.removeChild(child); res.write(parent.size()); 23
void removeChild(<HopObject> child)
res.write(parent.size()); 24 var child = parent.get(5); child.remove(); parent.removeChild(child); res.write(parent.size()); 23
child
- as HopObject
void renderSkin(<String> skin, <Object> params)
Contents of the file root/example.skin:   <title>Hello, <% param.title %>!</title>  <body bgcolor="<% param.bgcolor %>"> I greet you <% param.amount %> times.  Rendering the skin:
var param = new Object(); param.bgcolor = "#ffcc00"; param.title = "World"; param.amount = "12345"; root.renderSkin("example", param);   <title>Hello, World!</title>   I greet you 12345 times.
skin
- as String, the name of the skin to be rendered
params
- as Object, optional properties to be passed to the skin
String renderSkinAsString(<String> skin, <Object> params)
var str = root.renderSkinAsString("example", param); res.write(str); which is equivalent to root.renderSkin("example", param);
skin
- as String, the name of the skin to be rendered
params
- as Object, optional properties to be passed to the skin
void setParent(<HopObject> subnode)
var trash = user.stories.get(23); trash.setParent(root); root.remove(trash);
subnode
- as HopObject
Number size()
res.write(root.size()); 5
void size_macro(<Object> param, <String> name)
param
argument:
param
- The default macro parameter
name
- The default name for a child node
void skin_macro(param, name)
void switch_macro(param)
void update()
| SUMMARY: Constructor | Properties | Methods | DETAIL: Constructor | Properties | Methods |


Currently experiments DOES NOT support for many features: saving created workflows, real-time data processing, nice visualizations, ... and so on.
saving created workflows
real-time data processing
nice visualizations
This is not supported yet


CalculatoR
Made by: Elminster White
AC
CE
.
÷
7
8
9
×
4
5
6
-
1
2
3
+
0
=
CalculatoR
Made by: Elminster White
AC
CE
.
÷
7
8
9
×
4
5
6
-
1
2
3
+
0
=
CalculatoR
Made by: Elminster White
AC
CE
.
÷
7
8
9
×
4
5
6
-
1
2
3
+
0
=
Cloned calculators - example of reusable code


Like any other code completion in eclipse you start with CTRL + SPACE
and you
get the proposals.
The document is scanned for already existing words. Those words are available as proposals.
All keywords known by asciidoctor editor will be added as proposals
The different kind of proposals can be turned on/off inside
Preferences->AsciiDoctor Editor
.


Andria Dawson Mount Royal University
Simon J. Goring University of Wisconsin - Madison LIBED, May 16, 2019


The Free Republic of Liberland is a sovereign state located between Croatia and Serbia on the west bank of the Danube river. The nearest towns are Zmajevac (Croatia) and Bački Monoštor or Apatin (Serbia). The motto of the country is “To Live and Let Live”, following the rules of free trade and free market with absolute minimal State interference into people’s lives and business activities. Historically, this model has brought the highest level of development to societies, as demonstrated in countries like Singapore, Hong Kong, Liechtenstein, Switzerland, Monaco, and others.
Liberland, as the first sovereign country in History, will be based on a tokenized statehood model, where social freedoms are fixed in unchangeable, unmodifiable, and guaranteed smart contracts. On top of that, the Liberland Merit is the all-in-one cryptoasset that represents the holder’s voting power, currency, and collateral for a decentralised justice. This model is far ahead of what traditional states and societies are able to even consider, and will serve as a model for future societies.
Liberland has attracted a unique business community striving for excellence on a global level, comprising top entrepreneurs and companies from many industries, both high-tech: information technologies, cryptocurrencies, data security and cryptography, blockchain, innovation; as well as from more traditional industries: energy and renewables, hospitality, financial services, healthcare, transportation, manufacturing, and many others.
"Liberland can add 0.5% to 1% GDP to Serbia and Croatia and in 50 years between 28% and 64% growth. Trade works"
source: Liberland Economic Council and from LIBEK independent economic institute.


Note
Click here to download the full example code
Manipulation of the data dictionary¶
What you’ll learn: Learn to quickly manipulate the subjects connectivity dictionary, selecting sub-sets of connectivity matrices regarding behavioral group or variables.
Author: Dhaif BEKHA
Retrieve the example dataset¶
In this example, we will work directly on a pre-computed dictionary, that contain two set of connectivity matrices, from two different groups. The first group, called controls is a set of connectivity matrices from healthy seven years old children, and the second group called patients, is a set of connectivity matrices from seven years old children who have suffered a stroke. You can download the dictionary use in this example here. You will also need, the data table containing a set of continuous or categorical behavioral variable regarding all the subjects in the dictionary. You can download the table here. When downloaded, all the files must be stored in your home directory.
Modules import¶
from conpagnon.data_handling import dictionary_operations, atlas, data_management
from conpagnon.utils.folders_and_files_management import load_object
import pandas as pd
from pathlib import Path
import os
import seaborn as sns
import matplotlib.pyplot as plt
Out:
/home/dhaif/anaconda3/envs/conpagnon/lib/python3.7/site-packages/sklearn/externals/joblib/__init__.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
Load the data¶
We will first load the subjects connectivity dictionary, storing for each groups and subject, the connectivity matrices for different connectivity metric. We will also the corresponding data table.
# Fetch the path of the home directory
home_directory = str(Path.home())
# Load the dictionary containing the connectivity matrices
subjects_connectivity_matrices = load_object(
full_path_to_object=os.path.join(home_directory, 'raw_subjects_connectivity_matrices.pkl'))
# load the data table
data_table = pd.read_excel(os.path.join(home_directory, 'data_table.xlsx'))
print(data_table.to_markdown())
# For convenience, we shift the index
# of the dataframe to the subjects
# identifiers column
data_table = data_table.set_index(['subjects'])
Out:
| | subjects | Group | Sex | Lesion | score |
|---:|:---------------|:--------|:------|:---------|-----------:|
| 0 | sub04_rc110343 | P | M | G | 1.00484 |
| 1 | sub06_ml110125 | P | M | G | 3.83867 |
| 2 | sub07_lc110496 | P | M | G | -0.907201 |
| 3 | sub08_jl110342 | P | M | G | -4.26892 |
| 4 | sub10_dl120547 | P | M | G | -0.957913 |
| 5 | sub12_ab110489 | P | F | G | 3.21885 |
| 6 | sub13_vl110480 | P | M | G | -0.331407 |
| 7 | sub14_rs120006 | P | M | G | -1.05699 |
| 8 | sub17_eb120007 | P | F | G | 2.88928 |
| 9 | sub20_hd120032 | P | F | D | -5.33207 |
| 10 | sub21_yg120001 | P | M | D | -1.56495 |
| 11 | sub23_lf120459 | P | M | D | 3.80515 |
| 12 | sub24_ed110159 | P | M | D | -10.4086 |
| 13 | sub25_ec110149 | P | F | D | 1.78148 |
| 14 | sub26_as110192 | P | M | D | -3.93445 |
| 15 | sub30_zp130008 | P | F | G | 1.42485 |
| 16 | sub32_mp130025 | P | F | G | -1.2626 |
| 17 | sub34_jc130100 | P | M | G | 1.37514 |
| 18 | sub35_gc130101 | P | M | G | 3.66906 |
| 19 | sub37_la130266 | P | F | D | 3.77187 |
| 20 | sub38_mv130274 | P | M | D | 2.17901 |
| 21 | sub39_ya130305 | P | F | G | 1.08922 |
| 22 | sub41_sa130332 | P | F | D | 1.80184 |
| 23 | sub43_mc130373 | P | F | G | 2.01819 |
| 24 | sub44_av130474 | P | F | G | -3.84236 |
| 25 | sub01_nc110193 | C | F | nan | nan |
| 26 | sub02_ib110200 | C | M | nan | nan |
| 27 | sub03_ct110201 | C | F | nan | nan |
| 28 | sub04_eb110217 | C | F | nan | nan |
| 29 | sub05_gk110258 | C | M | nan | nan |
| 30 | sub06_al110271 | C | M | nan | nan |
| 31 | sub08_cd090095 | C | F | nan | nan |
| 32 | sub09_sl100362 | C | M | nan | nan |
| 33 | sub10_ag110427 | C | M | nan | nan |
| 34 | sub11_nn110428 | C | F | nan | nan |
| 35 | sub12_at110408 | C | M | nan | nan |
| 36 | sub14_rp120164 | C | M | nan | nan |
| 37 | sub16_cg120322 | C | F | nan | nan |
| 38 | sub17_cm120095 | C | M | nan | nan |
| 39 | sub18_cb130208 | C | F | nan | nan |
| 40 | sub19_cd120206 | C | M | nan | nan |
| 41 | sub20_mp120048 | C | M | nan | nan |
| 42 | sub21_sb120208 | C | F | nan | nan |
| 43 | sub22_ln120402 | C | M | nan | nan |
| 44 | sub23_kf130380 | C | F | nan | nan |
| 45 | sub24_ls130404 | C | F | nan | nan |
| 46 | sub25_sv120315 | C | F | nan | nan |
| 47 | sub26_ep120255 | C | M | nan | nan |
| 48 | sub27_ea130507 | C | F | nan | nan |
| 49 | sub28_ml130538 | C | F | nan | nan |
| 50 | sub29_hd130539 | C | F | nan | nan |
This data table have a very common structure with a mix of categorical and continous variable. Let’s barplot the score for the group of female and male in the patients population:
sns.barplot(x='Sex', y='score', data=data_table)
plt.show()
Out:
/media/dhaif/Samsung_T5/Work/Programs/ConPagnon/examples/05_utilities/plot_selection_of_data.py:74: UserWarning: Matplotlib is currently using agg, which is a non-GUI backend, so cannot show the figure.
plt.show()
Selecting a subset of data¶
It’s common to extract and compute the connectivity matrices on your whole cohort of data, and entering them in one or multiple statistical analysis. In practice, you may want only selecting a sub-set of your connectivity matrices. For example, you might want to select inside the patients group, the left lesioned subject and male only. For convenience, and avoiding a fastidious manual extraction inside the subjects connectivity matrices dictionary, we create a special function dedicated to this task. The main inputs are the connectivity dictionary of your population and the corresponding table.
# Select the male, and left lesioned
# patients.
# Select a subset of patients
# Compute the connectivity matrices dictionary with factor as keys.
group_by_factor_subjects_connectivity, population_df_by_factor, factor_keys, = \
dictionary_operations.groupby_factor_connectivity_matrices(
population_data_file=os.path.join(home_directory, 'data_table.xlsx'),
sheetname='behavioral_data',
subjects_connectivity_matrices_dictionnary=subjects_connectivity_matrices,
groupes=['patients'], factors=['Lesion', 'Sex'])
The groupby_factor_connectivity_matrices()
output 3 objects: group_by_factor_subjects_connectivity
is a dictionary
with all possible combination of the factors
list you’ve entered. Here,
we entered Lesion, and Sex, two categorical variable with 2 levels
each. So number of keys of the groupby_factor_connectivity_matrices
dictionary should be 2x2, 4: the right lesioned AND female patients,
the right lesioned AND male patients, the left lesioned AND male patients,
the left lesioned AND female patients. Let’s print out the keys list
to verify it:
print(list(group_by_factor_subjects_connectivity.keys()))
Out:
[('D', 'F'), ('D', 'M'), ('G', 'F'), ('G', 'M')]
The second output is another dictionary, with the previous list as key, and the list of subjects for each sub-group. For example, let’s print out the list of subjects in the male right lesioned group:
print(population_df_by_factor[('D', 'M')])
Out:
Index(['sub21_yg120001', 'sub23_lf120459', 'sub24_ed110159', 'sub26_as110192',
'sub38_mv130274'],
dtype='object')
The last output is simply the keys list of the new group:
print(factor_keys)
Out:
[('D', 'F'), ('D', 'M'), ('G', 'F'), ('G', 'M')]
Now, we can create a new dictionary of patients that contains only the sub-group we wanted: the left lesioned and male patients. It’s easy, because you just computed it:
left_lesioned_male_matrices = dict()
left_lesioned_male_matrices['patients'] = group_by_factor_subjects_connectivity[('G', 'M')]
Total running time of the script: ( 0 minutes 0.588 seconds)


CPP-API: Interface to the file system.
More...
Inherits Intern::AllocateFromAssimpHeap.
Inherited by Assimp::BlobIOSystem, Assimp::CIOSystemWrapper, Assimp::DefaultIOSystem, Assimp::FileSystemFilter, Assimp::MemoryIOSystem, and Assimp::ZipArchiveIOSystem.
|
| | IOSystem () AI_NO_EXCEPT |
| | Default constructor. More...
|
| |
| virtual | ~IOSystem () |
| | Virtual destructor. More...
|
| |
| virtual bool | ChangeDirectory (const std::string &path) |
| | Will change the current directory to the given path. More...
|
| |
| virtual void | Close (IOStream *pFile)=0 |
| | Closes the given file and releases all resources associated with it. More...
|
| |
| virtual bool | ComparePaths (const char *one, const char *second) const |
| | Compares two paths and check whether the point to identical files. More...
|
| |
| bool | ComparePaths (const std::string &one, const std::string &second) const |
| | For backward compatibility. More...
|
| |
| virtual bool | CreateDirectory (const std::string &path) |
| | CReates an new directory at the given path. More...
|
| |
| virtual const std::string & | CurrentDirectory () const |
| | Returns the top directory from the stack. More...
|
| |
| virtual bool | DeleteFile (const std::string &file) |
| |
| virtual bool | Exists (const char *pFile) const =0 |
| | Tests for the existence of a file at the given path. More...
|
| |
| AI_FORCE_INLINE bool | Exists (const std::string &pFile) const |
| | For backward compatibility. More...
|
| |
| virtual char | getOsSeparator () const =0 |
| | Returns the system specific directory separator. More...
|
| |
| virtual IOStream * | Open (const char *pFile, const char *pMode="rb")=0 |
| | Open a new file with a given path. More...
|
| |
| IOStream * | Open (const std::string &pFile, const std::string &pMode=std::string("rb")) |
| | For backward compatibility. More...
|
| |
| virtual bool | PopDirectory () |
| | Pops the top directory from the stack. More...
|
| |
| virtual bool | PushDirectory (const std::string &path) |
| | Pushes a new directory onto the directory stack. More...
|
| |
| virtual size_t | StackSize () const |
| | Returns the number of directories stored on the stack. More...
|
| |
CPP-API: Interface to the file system.
Derive an own implementation from this interface to supply custom file handling to the importer library. If you implement this interface, you also want to supply a custom implementation for IOStream.
- See also
- Importer::SetIOHandler()
◆ IOSystem()
◆ ~IOSystem()
Virtual destructor.
It is safe to be called from within DLL Assimp, we're constructed on Assimp's heap.
◆ ChangeDirectory()
| AI_FORCE_INLINE bool Assimp::IOSystem::ChangeDirectory |
( |
const std::string & |
path | ) |
|
|
virtual |
◆ Close()
| virtual void Assimp::IOSystem::Close |
( |
IOStream * |
pFile | ) |
|
|
pure virtual |
◆ ComparePaths() [1/2]
| bool IOSystem::ComparePaths |
( |
const char * |
one, |
|
|
const char * |
second |
|
) |
| const |
|
virtual |
Compares two paths and check whether the point to identical files.
The dummy implementation of this virtual member performs a case-insensitive comparison of the given strings. The default IO system implementation uses OS mechanisms to convert relative into absolute paths, so the result can be trusted.
- Parameters
-
| one | First file |
| second | Second file |
- Returns
- true if the paths point to the same file. The file needn't be existing, however.
Reimplemented in Assimp::MemoryIOSystem, Assimp::DefaultIOSystem, and Assimp::FileSystemFilter.
◆ ComparePaths() [2/2]
| AI_FORCE_INLINE bool Assimp::IOSystem::ComparePaths |
( |
const std::string & |
one, |
|
|
const std::string & |
second |
|
) |
| const |
|
inline |
For backward compatibility.
- See also
- ComparePaths(const char*, const char*)
◆ CreateDirectory()
| AI_FORCE_INLINE bool Assimp::IOSystem::CreateDirectory |
( |
const std::string & |
path | ) |
|
|
virtual |
CReates an new directory at the given path.
- Parameters
-
| path | [in] The path to create. |
- Returns
- True, when a directory was created. False if the directory cannot be created.
Reimplemented in Assimp::MemoryIOSystem, and Assimp::FileSystemFilter.
◆ CurrentDirectory()
| AI_FORCE_INLINE const std::string & Assimp::IOSystem::CurrentDirectory |
( |
| ) |
const |
|
virtual |
◆ DeleteFile()
| AI_FORCE_INLINE bool Assimp::IOSystem::DeleteFile |
( |
const std::string & |
file | ) |
|
|
virtual |
◆ Exists() [1/2]
| virtual bool Assimp::IOSystem::Exists |
( |
const char * |
pFile | ) |
const |
|
pure virtual |
◆ Exists() [2/2]
| AI_FORCE_INLINE bool Assimp::IOSystem::Exists |
( |
const std::string & |
pFile | ) |
const |
For backward compatibility.
- See also
- Exists(const char*)
◆ getOsSeparator()
| virtual char Assimp::IOSystem::getOsSeparator |
( |
| ) |
const |
|
pure virtual |
◆ Open() [1/2]
| virtual IOStream* Assimp::IOSystem::Open |
( |
const char * |
pFile, |
|
|
const char * |
pMode = "rb" |
|
) |
| |
|
pure virtual |
Open a new file with a given path.
When the access to the file is finished, call Close() to release all associated resources (or the virtual dtor of the IOStream).
- Parameters
-
| pFile | Path to the file |
| pMode | Desired file I/O mode. Required are: "wb", "w", "wt", "rb", "r", "rt". |
- Returns
- New IOStream interface allowing the lib to access the underlying file.
- Note
- When implementing this class to provide custom IO handling, you probably have to supply an own implementation of IOStream as well.
Implemented in Assimp::ZipArchiveIOSystem, Assimp::MemoryIOSystem, Assimp::DefaultIOSystem, Assimp::FileSystemFilter, Assimp::CIOSystemWrapper, and Assimp::BlobIOSystem.
◆ Open() [2/2]
| AI_FORCE_INLINE IOStream * Assimp::IOSystem::Open |
( |
const std::string & |
pFile, |
|
|
const std::string & |
pMode = std::string("rb") |
|
) |
| |
|
inline |
◆ PopDirectory()
◆ PushDirectory()
| AI_FORCE_INLINE bool Assimp::IOSystem::PushDirectory |
( |
const std::string & |
path | ) |
|
|
virtual |
◆ StackSize()
◆ m_pathStack
| std::vector<std::string> Assimp::IOSystem::m_pathStack |
|
private |
The documentation for this class was generated from the following files:


--- layout: archive title: Zulip Chat Archive permalink: /stream/144837-PR-reviews/topic/.23822.20Compute.20the.20first.20three.20digits.20of.20pi.html ---
This didn't get merged in month floor π
. Let's get it merged on April Fools Day!
the github constraints are kind of annoying... you can't merge stuff without first updating the branch, even if there are no conflicts, and then it takes an hour before travis runs... I used my admin privileges to merge anyway this time
That's not specific to this PR, right?
no
And we don't want Travis to use even more caches, because there should be some place where we recompile from scratch
but if I have a few minutes to look at PRs usually I only have time to update the branch, then travis runs, and I get pulled away... and I come back and something else has merged in the meantime and we are back to square one
Yep, I understand.
Which means that we need to fix some workflow issues.
I think it should be okay to merge a branch that is not up to date if github can merge automatically
there is a small possibility of travis breakage
Hmmm... green lights from Travis don't mean much if they are several weeks old
For example, you might need to bump up type class search depth. That has occurred a couple of times lately.
@Mario Carneiro Anyway, thanks for merging!
@Mario Carneiro @Simon Hudon @Scott Morrison Is there something that we can do about this issue?
Because it's not good if merging PRs becomes an annoying bureaucratic dance...
I think the larger the PRs the worse it will be
@Simon Hudon Why's that? I got the impression from Mario that it will just be one hour of Travis-compiling before each merge...
With smaller PRs, it's easier to take the risk and just merge even if it's not completely up to master
Right...
Could we let Travis use cache-olean
somehow?
It already does
The other thing we can do is reduce inter-modular dependencies. That will bring re-build time down
I haven't followed this whole saga. How much of a nightmare is it actually?
So why is it taking > 1hr
to check?
That just means we get very bad VMs
Maybe we need to reconsider running our own CI.
Because if this is creating a frustrating experience for maintainers, then we get a frustrating experience for contributors, and we end up with a frustrated community...
Look at the PR queue to get an idea of the nightmare.
Is the number of PRs we receive increasing or are we getting worse at handling them?
Maybe a bit of both
What makes you say that? The queue grows but if it's just because we get more requests, it's only an indicator of our popularity
The growth of the queue has made me very reluctant to start PR'ing the stuff we have in the perfectoid project. https://github.com/leanprover-community/lean-perfectoid-spaces/tree/master/src/for_mathlib there's what we have waiting for you. But what's the point of just adding it to the pile?
Beside making the build faster, what do you guys think would make the situation better?
It was Mario's post above which concerned me. Making it easier for Mario would make the situation better.
You mean?
Mario Carneiro: but if I have a few minutes to look at PRs usually I only have time to update the branch, then travis runs, and I get pulled away... and I come back and something else has merged in the meantime and we are back to square one
Yes that.
Ok, no matter how fast we make the build, we're not going to fix this without a change of workflow
Yes I see.
In my opinion it's not that big a deal if the master branch occasionally fails to build, particularly when we have the lean-3.4.2
branch head which is always supposed to build.
Every time a PR is merged there are now 50 PR's which need updating to mathlib master. The question is whether to update them all or to gamble.
@Mario Carneiro when you update a branch which you're ready to merge, you can tag it as "ready-to-merge" and post on the maintainer channel to ask someone available to merge it when it's done building.
I would vote for merging without check, and then fixing if needed.
for small PRs I agree
For larger PR, the best might be to have a sort of merge queue: we update the head of the queue, when it builds we merge it and then do the same for the next.
right now only I and other admins have permission to merge without check. Some github option is causing a problem?
I agree with Reid that 3.4.2
is stable and will always build. So it doesn't matter too much if master sometimes breaks. I also like Simon's proposal of a "ready-to-merge" queue.
https://mergify.io Free for open source repositories.
{% endraw %}Last updated: Apr 24 2020 at 19:02 UTC


Email :
<EMAIL_ADDRESS>Call :
8876 7786 999
Toggle navigation
Home
Homepage variation-1
Homepage variation-2
Homepage variation-3
about us
doctors
services
news
pages
Blog
Blog details
Doctors timetable
404 error
Appointment
contact us
Appointment
Doctors
met our
experts
filter
select departments
USA
Canada
France
Spain
Bulgaria
Greece
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Dr. Vasudevayyar MBBS
cardiology
Medical Theme © 2015 | All Rights Reserved


Introduction¶
Welcome to the Yahtzee API! This package provides the core functionalities to programmatically play a game of Yahtzee. The purpose of this package is for use with reinforcement learning environments (in development), however it is generalized for many different use cases including simple algorithm development. Instantiating a Game object will create a list of Player objects that can be interacted with using the methods outlined in these docs. Click into the links on the left panel for a detailed description of the public methods and attributes for each class.
GitHub Repo¶
To view the source code and examples for the Yahtzee API, visit the GitHub repo here here.
Installation¶
To install this package, run: pip install yahtzee-api
A Note on Versioning¶
This project is my first headfirst dive into the world of publishing Python packages, using Sphinx for documentation, GitHub Actions, etc. As such, there are plenty of junk commits and mistakes in the repo. I’ve done my best to clean it up and make sure that what is presented is accurate, up-to-date, and at least somewhat helpful. Canonically, v0.1.2 is the first release of this package. Yes, v0.1.0 and v0.1.1 existed, but both fell victim to my inexperience with Python publishing (amongst other things). From v0.1.2 on, all changes and versioning will following semantic versioning guidelines specified by semver.


My Team
Manager Person
Manager
Employee ID: 1
Employee Email:
<EMAIL_ADDRESS>Office Number: 1
Engineer Person
Engineer
Employee ID: 2
Employee Email:
<EMAIL_ADDRESS>Employee GitHub:
engineer
Intern Person
Intern
Employee ID: 3
Employee Email:
<EMAIL_ADDRESS>School: UCLA