|
原帖地址:http://www.flexsim.com/community/forum/showthread.php?t=2881
0 Z" i7 {: C1 P' l, g0 V3 p8 ]1 v1 Z) p) k8 I2 \0 W
下载模型可以去原帖上面进行~~~
# j; x& R" a8 V8 d; E0 @0 f5 U9 {/ v6 u7 t, c, l6 Q
节选里面的模型作用介绍
* |, B$ q: I& Z4 l5 i4 m% d“Hi community!
( R" q. H" I# `3 g6 E; ~! X 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.
5 p$ d1 c( i9 }- D6 L% b, H, F9 e
6 C" R, I3 Y k2 s0 L- u% m, s. h+ m+ I2 H2 S
Restrictions for this beta:
2 y+ H1 P5 Q2 ^6 ~; Z! a - no gui
* }2 z! g/ ]# T3 z1 M+ y" S - only for 64 bit
2 h0 B9 ?0 O: {% F' E - tested only with FlexSim GP 7.1.4 64bit on a Windows 7 64bit4 r h. L4 A0 F( b2 Z" W1 G0 x" {
4 \" H# n0 a1 F6 }/ |5 [5 o4 u
5 |. A, o+ j2 \; S$ H0 Z How to install?
* g4 Z& w/ d; t Unzip file to modules folder in flexsim.0 ]1 J3 i1 C& F
9 y% z1 Y0 h. L2 F
" H- \. F1 S- z: J7 {
How to use?
$ |' M0 l) i* D. \1 _: x1 B7 C Just drag your new HeatmapTicker object into your model. That's it.
" Q W# {+ T$ i1 W
( W# ?0 a& O2 |( P; b. J5 H# A9 a3 ^
What does this module? D( }; g2 J$ ]3 q- O
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.
' |, a0 g( Z. H3 n/ O Which settings options are available?4 |- U! ~ R5 ] N
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:' s2 l: A2 ?) O+ {' D4 e' o
- ticktime -> time interval to add the actual location of your taskexecuters, j2 ^6 v1 B" m! d8 }+ i( {3 C, M
- gridsizeX -> area in x to summarize locations/ J2 N' e$ S' J n1 w3 h
- gridsizeY -> area in y to summarize locations3 E2 D6 X9 l5 ]0 ]
- sizeZ -> if greater than 0, your heatmap goes up in the sky % g" C9 l. X: }5 w% u
- objectList -> only for your information, which taskexecuters are registered for the heatmap (robot and elevators aren't added)6 G) ]9 F' }9 h" s5 m/ L
- mesh -> heatmap drawing, don't touch
2 d$ P. C% Q2 M4 o% T You can make you heatmap invisible if you use the flexsim command switch_hideshape.* X8 o! F9 J6 j+ E0 Y, q& Z- A
8 i& `; ]1 b1 e y
+ @ r# z) G- R: b1 [+ f8 B Hints:
2 x8 J- s ^% f7 P: p" }9 q! W, k# i - very small ticktime, gridsizeX and/or gridsizeY boost your cpu usage
9 Y- G* t6 r4 x8 D. L; ? - only taskexecuters in the model tree will be recognized
! L3 e: K) g) V4 l" _) g - only used locations will be stored -> no restrictions for locations/ a1 g# e' _* E0 o) H
- the colors and optional heights aren't linear -> a natural logarithm will be used with the measured data to make the heatmap more visible7 A6 [! w4 R. G2 r8 p3 Y
# q- s1 I$ U) k1 B6 f' [' c
I'm curious about your thoughts and hints. Of course you'll get the final version also. Did I mentioned that it's free? 1 b# j% Y! ?/ h4 K% C- |
” |
|