|
原帖地址:http://www.flexsim.com/community/forum/showthread.php?t=2881. G3 {# J* E9 Y1 \1 i: Y
; d. W' Y* L- Z0 x" K. Z) B; [9 d下载模型可以去原帖上面进行~~~
0 U. f, u# K$ ~3 L$ |6 M
6 v& t/ ~$ ~+ B% r节选里面的模型作用介绍) A& q I6 `8 ~5 }! e
“Hi community!
( m* D* u* T; d- B D" ~8 R I've a little something for you ;-) I've developed a little module to show a heatmap in our models. It's brandnew and still beta but I'm interested in our opinion.4 D( c5 F6 e: v8 G
% F3 b6 I: d$ ]8 H% n3 {% X
" X9 k% j2 `# s Restrictions for this beta:: S/ q, m) q% f; [( Y
- no gui0 I; X% z4 C" j5 k" A
- only for 64 bit
. ?3 H7 \5 U/ _3 v5 q - tested only with FlexSim GP 7.1.4 64bit on a Windows 7 64bit; W4 Z7 C7 O% {9 H0 n
2 p: ~- f' m5 Q4 s8 r
W) {% N P2 J9 F g How to install?' ]3 r3 I+ a$ _$ I3 T2 I
Unzip file to modules folder in flexsim.) o2 m1 q9 e* H0 K ] U4 {1 b2 _
2 X5 p' {4 L! n9 ^4 P3 z4 W$ g4 R; m% A" N, A$ {
How to use?, |; K* k2 }$ n, {
Just drag your new HeatmapTicker object into your model. That's it.
+ m7 Q/ O) c0 f
- `& j2 l" t$ z: d* |% n+ g8 }4 f; E: l3 c& H3 O
What does this module?& P; {* z- _' J2 T# H! ? c! E! w
This module draw a heatmap in your model. It collects the location of your taskexecuters for each tick of the heatmapticker. This shows you how often a location was used. Red means a hot area and blue a cold area.1 W( n x% c1 H$ T5 ?+ g
Which settings options are available?
$ H9 p% j) y- v3 G: t Z* x Even without a gui you have several options to configure your heatmap. You have to access your heatmapticker with the tree view. The settings are in the variables node:$ g. ~- i3 ~) L. Q4 G
- ticktime -> time interval to add the actual location of your taskexecuters9 X2 S1 v1 t% k% D0 d& e+ z
- gridsizeX -> area in x to summarize locations
) e7 Z4 x% w ^7 g4 m# G3 ? - gridsizeY -> area in y to summarize locations4 [9 `8 Z- {2 C( R
- sizeZ -> if greater than 0, your heatmap goes up in the sky
9 l: w$ r1 d7 t" v- {- t - objectList -> only for your information, which taskexecuters are registered for the heatmap (robot and elevators aren't added)
9 o! b6 k/ ]( ?! ^. ~; D/ S - mesh -> heatmap drawing, don't touch; m( U* T2 v, X9 K: Y- n, }
You can make you heatmap invisible if you use the flexsim command switch_hideshape./ I% Q- s) A m% v6 ]/ _
% b7 N6 B% x- w: T' i! |# g3 t1 z* G
Hints:# o; W* e+ i) S* I$ \2 ^
- very small ticktime, gridsizeX and/or gridsizeY boost your cpu usage j+ P4 n2 x3 y. }0 G+ H
- only taskexecuters in the model tree will be recognized
$ S$ b0 C( L7 A- U - only used locations will be stored -> no restrictions for locations E' C/ a" j( g; {" A8 Z) s
- the colors and optional heights aren't linear -> a natural logarithm will be used with the measured data to make the heatmap more visible2 ^3 e/ |* t# ^- T2 \5 U* f3 E
7 _; r( q( y' L; u% H: V
I'm curious about your thoughts and hints. Of course you'll get the final version also. Did I mentioned that it's free? 8 _; N0 {: \3 n# Z0 G
” |
|