Webvideocap 1 41 0 0 0

00:41:17.597: ISAKMP: local port 500, remote port 500*Mar 2 00:41:17.597: ISAKMP (0:1): beginning Main Mode exchange*Mar 2 00:41:17.597: ISAKMP (0:1): sending packet to 200.1.1.1 (I) MM_NO_STATE*Mar 2 00:41:17.773: ISAKMP (0:1): received packet from 200.1.1.1 (I) MM_NO_STATE*Mar 2 00:41:17.773: ISAKMP (0:1): processing SA payload. message ID = 0*Mar 2 00:41:17.773: ISAKMP (0:1): found peer pre-shared key matching 200.1.1.1*Mar 2 00:41:17.773: ISAKMP (0:1): Checking ISAKMP transform 1 against priority 10 policy!--- IKE SAs are negotiated.*Mar 2 00:41:17.773: ISAKMP: encryption DES-CBC*Mar 2 00:41:17.773: ISAKMP: hash SHA*Mar 2 00:41:17.773: ISAKMP: default group 2*Mar 2 00:41:17.773: ISAKMP: auth pre-share*Mar 2 00:41:17.773: ISAKMP: life type in seconds*Mar 2 00:41:17.773: ISAKMP: life duration (basic) of 3600*Mar 2 00:41:17.773: ISAKMP (0:1): atts are acceptable. Next payload is 0*Mar 2 00:41:17.773: CryptoEngine0: generate alg parameter*Mar 2 00:41:17.905: CRYPTO_ENGINE: Dh phase 1 status: 0*Mar 2 00:41:17.905: CRYPTO_ENGINE: Dh phase 1 status: 0*Mar 2 00:41:17.905: ISAKMP (0:1): SA is doing pre-shared key authentication using id type ID_IPV4_ADDR*Mar 2 00:41:17.905: ISAKMP (0:1): sending packet to 200.1.1.1 (I) MM_SA_SETUP*Mar 2 00:41:18.149: ISAKMP (0:1): received packet from 200.1.1.1 (I) MM_SA_SETUP*Mar 2 00:41:18.153: ISAKMP (0:1): processing KE payload. message ID = 0*Mar 2 00:41:18.153: CryptoEngine0: generate alg parameter*Mar 2 00:41:18.317: ISAKMP (0:1): processing NONCE payload. message ID = 0*Mar 2 00:41:18.317: ISAKMP (0:1): found peer pre-shared key matching 200.1.1.1*Mar 2 00:41:18.317: CryptoEngine0: create ISAKMP SKEYID for conn id 1*Mar 2 00:41:18.321: ISAKMP (0:1): SKEYID state generated*Mar 2 00:41:18.321: ISAKMP (0:1): processing vendor id payload*Mar 2 00:41:18.321: ISAKMP (0:1): speaking to another IOS box!*Mar 2 00:41:18.321:

Of 0x0 0x46 0x50 0x0*Mar 2 00:41:18.685: ISAKMP: authenticator is HMAC-MD5*Mar 2 00:41:18.685: validate proposal 0*Mar 2 00:41:18.685: ISAKMP (0:1): atts are acceptable.*Mar 2 00:41:18.685: IPSEC(validate_proposal_request): proposal part #1, (key eng. msg.) INBOUND local= 100.1.1.1, remote= 200.1.1.1, local_proxy= 150.0.0.1/255.255.255.255/47/0 (type=1), remote_proxy= 150.0.0.2/255.255.255.255/47/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 0s and 0kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4*Mar 2 00:41:18.689: validate proposal request 0*Mar 2 00:41:18.689: ISAKMP (0:1): processing NONCE payload. message ID = -2078851837*Mar 2 00:41:18.689: ISAKMP (0:1): processing ID payload. message ID = -2078851837*Mar 2 00:41:18.689: ISAKMP (0:1): processing ID payload. message ID = -2078851837*Mar 2 00:41:18.689: CryptoEngine0: generate hmac context for conn id 1*Mar 2 00:41:18.689: ipsec allocate flow 0*Mar 2 00:41:18.689: ipsec allocate flow 0!--- IPSec SAs are generated for inbound and outbound traffic.*Mar 2 00:41:18.693: ISAKMP (0:1): Creating IPSec SAs*Mar 2 00:41:18.693: inbound SA from 200.1.1.1 to 100.1.1.1 (proxy 150.0.0.2 to 150.0.0.1)*Mar 2 00:41:18.693: has spi 0x9AAD0079 and conn_id 2000 and flags 4*Mar 2 00:41:18.693: lifetime of 3600 seconds*Mar 2 00:41:18.693: lifetime of 4608000 kilobytes*Mar 2 00:41:18.693: outbound SA from 100.1.1.1 to 200.1.1.1 (proxy 150.0.0.1 to 150.0.0.2 )*Mar 2 00:41:18.693: has spi -1609905338 and conn_id 2001 and flags C*Mar 2 00:41:18.693: lifetime of 3600 seconds*Mar 2 00:41:18.693: lifetime of 4608000 kilobytes*Mar 2 00:41:18.697: ISAKMP (0:1): sending packet to 200.1.1.1 (I) QM_IDLE*Mar 2 00:41:18.697: ISAKMP (0:1): deleting node -2078851837 error FALSE reason ""*Mar 2 00:41:18.697: IPSEC(key_engine): got a queue event...*Mar 2 00:41:18.697: IPSEC(initialize_sas): , (key eng. msg.) INBOUND local= 100.1.1.1, remote= 200.1.1.1, local_proxy=

ISAKMP (1): ID payload next-payload : 8 type : 1 protocol : 17 port : 500 length : 8*Mar 2 00:41:18.321: ISAKMP (1): Total payload length: 12*Mar 2 00:41:18.321: CryptoEngine0: generate hmac context for conn id 1*Mar 2 00:41:18.321: ISAKMP (0:1): sending packet to 200.1.1.1 (I) MM_KEY_EXCH*Mar 2 00:41:18.361: ISAKMP (0:1): received packet from 200.1.1.1 (I) MM_KEY_EXCH*Mar 2 00:41:18.361: ISAKMP (0:1): processing ID payload. message ID = 0*Mar 2 00:41:18.361: ISAKMP (0:1): processing HASH payload. message ID = 0*Mar 2 00:41:18.361: CryptoEngine0: generate hmac context for conn id 1!--- Peer is authenticated.*Mar 2 00:41:18.361: ISAKMP (0:1): SA has been authenticated with 200.1.1.1!--- Begins quick mode exchange.*Mar 2 00:41:18.361: ISAKMP (0:1): beginning Quick Mode exchange, M-ID of -2078851837*Mar 2 00:41:18.365: CryptoEngine0: generate hmac context for conn id 1*Mar 2 00:41:18.365: ISAKMP (0:1): sending packet to 200.1.1.1 (I) QM_IDLE*Mar 2 00:41:18.365: CryptoEngine0: clear dh number for conn id 1*Mar 2 00:41:18.681: ISAKMP (0:1): received packet from 200.1.1.1 (I) QM_IDLE*Mar 2 00:41:18.681: CryptoEngine0: generate hmac context for conn id 1*Mar 2 00:41:18.685: ISAKMP (0:1): processing HASH payload. message ID = -2078851837*Mar 2 00:41:18.685: ISAKMP (0:1): processing SA payload. message ID = -2078851837!--- Negotiates IPSec SA.*Mar 2 00:41:18.685: ISAKMP (0:1): Checking IPSec proposal 1*Mar 2 00:41:18.685: ISAKMP: transform 1, ESP_DES*Mar 2 00:41:18.685: ISAKMP: attributes in transform:*Mar 2 00:41:18.685: ISAKMP: encaps is 1*Mar 2 00:41:18.685: ISAKMP: SA life type in seconds*Mar 2 00:41:18.685: ISAKMP: SA life duration (basic) of 3600*Mar 2 00:41:18.685: ISAKMP: SA life type in kilobytes*Mar 2 00:41:18.685: ISAKMP: SA life duration (VPI)

Edges of a vertex use .outE() .Label is optional and if passed the outgoing edges will be filtered by that labelExample:gremlin> g.V('#41:1').outE()==>e[#221:6][#41:1-HasFriend->#42:1]==>e[#222:6][#41:1-HasFriend->#43:1]To display all the incoming edges of a vertex use .inE(). Example:gremlin> g.V('#41:1').inE()==>e[#224:0][#41:0-HasFriend->#41:1]==>e[#217:2][#42:0-HasFriend->#41:1]==>e[#217:3][#43:0-HasFriend->#41:1]==>e[#224:3][#44:0-HasFriend->#41:1]==>e[#222:4][#45:0-HasFriend->#41:1]==>e[#219:5][#46:0-HasFriend->#41:1]==>e[#223:5][#47:0-HasFriend->#41:1]==>e[#218:6][#48:0-HasFriend->#41:1]==>e[#185:0][#121:0-HasProfile->#41:1]For more information look at the Gremlin Traversal.Filter resultsThis example returns all the outgoing edges of all the vertices with label equal to 'friend'.gremlin> g.V('#41:1').inE('HasProfile')==>e[#185:0][#121:0-HasProfile->#41:1]gremlin> Create complex pathsGremlin allows you to concatenate expressions to create more complex traversals in a single line:g.V().in().out()Of course this could be much more complex. Below is an example with the graph taken from the official documentation:gremlin> g.V('44:0').out('HasFriend').out('HasFriend').values('Name').dedup()==>Frank==>Emanuele==>Paolo==>Colin==>Andrey==>Sergeygremlin> Gremlin ServerThere are two ways to use OrientDB inside the Gremlin ServerUse the OrientDB-TP3 distribution that embed the Gremlin ServerInstall the OrientDB-Gremlin Driver into a GremlinServerOrientDB-TP3Download the latest version of OrientDB-TP3 here.and start OrientDB to automatically start the embedded Gremlin Server.The configuration of the Gremlin Server is in $ORIENTDB_HOME/config.When using the embedded version by default the Authentication manager authenticate the users against OrientDB server userwith permission gremlin.server.Install OrientDB-GremlinDownload the latest Gremlin Server distribution hereand then install the OrientDB Gremlin driver with bin/gremlin-server.sh -i com.orientechnologies orientdb-gremlin ${version}OrientDB Gremlin Server configurationYAML configuration example (save as gremlin-server.yaml)host: localhostport: 8182scriptEvaluationTimeout: 30000channelizer: org.apache.tinkerpop.gremlin.server.channel.WebSocketChannelizergraphs: { graph : conf/orientdb-empty.properties}scriptEngines: { gremlin-groovy: { plugins: { org.apache.tinkerpop.gremlin.server.jsr223.GremlinServerGremlinPlugin: {}, org.apache.tinkerpop.gremlin.orientdb.jsr223.OrientDBGremlinPlugin: {}, org.apache.tinkerpop.gremlin.jsr223.ImportGremlinPlugin: {classImports: [java.lang.Math], methodImports: [java.lang.Math#*]}, org.apache.tinkerpop.gremlin.jsr223.ScriptFileGremlinPlugin: {files: [ scripts/empty-sample.groovy]}}}}serializers: - { className: org.apache.tinkerpop.gremlin.driver.ser.GryoMessageSerializerV3d0, config: { ioRegistries: [org.apache.tinkerpop.gremlin.orientdb.io.OrientIoRegistry] }} # application/vnd.gremlin-v3.0+gryo - { className: org.apache.tinkerpop.gremlin.driver.ser.GryoMessageSerializerV3d0, config: { serializeResultToString: true }} # application/vnd.gremlin-v3.0+gryo-stringd - { className: org.apache.tinkerpop.gremlin.driver.ser.GraphSONMessageSerializerV3d0, config: { ioRegistries: [org.apache.tinkerpop.gremlin.orientdb.io.OrientIoRegistry] }} # application/jsonprocessors: - { className: org.apache.tinkerpop.gremlin.server.op.session.SessionOpProcessor, config: { sessionTimeout: 28800000 }} - { className: org.apache.tinkerpop.gremlin.server.op.traversal.TraversalOpProcessor, config: { cacheExpirationTime: 600000, cacheMaxSize: 1000 }}metrics: { consoleReporter: {enabled: true, interval: 180000}, csvReporter: {enabled: true, interval: 180000, fileName: /tmp/gremlin-server-metrics.csv}, jmxReporter: {enabled: true}, slf4jReporter: {enabled: true, interval: 180000}}strictTransactionManagement: falsemaxInitialLineLength: 4096maxHeaderSize: 8192maxChunkSize: 8192maxContentLength: 65536maxAccumulationBufferComponents: 1024resultIterationBatchSize: 64writeBufferLowWaterMark: 32768writeBufferHighWaterMark: 65536ssl: { enabled: false}Graph Configuration properties example (e.g. save as orientdb-empty.properties. It has to be the one referenced in the gremlin-server.yaml file)gremlin.graph=org.apache.tinkerpop.gremlin.orientdb.OrientFactoryorient-url=plocal:/tmp/graphorient-user=adminorient-pass=adminNote: currently is missing. Download and add to lib or plugins folder.OrientDB TinkerPop Graph APIIn order to use the OrientDB TinkerPop Graph API implementation, you need to create an instance of the

- 03/24 00:15 Full A.Bilbao (Aladdin) 0 - 1 A.Madrid (val) +0.5 1 - 1 1 - 1 3.5, 4.0 Under 43 - 37 - 1 03/24 00:15 Full Villarreal (Pele) 2 - 1 Barcelona (Nio) -0.5 1 - 0 1 - 0 3.0, 3.5 Under 40 - 42 2 - 1 03/24 00:00 Full Villarreal (Pele) 1 - 2 A.Madrid (val) -0.5, -1.0 2 - 0 2 - 0 3.5, 4.0 Under 48 - 41 1 - 2 03/23 23:30 Full Barcelona (Nio) 0 - 1 A.Madrid (val) +0.5 3 - 0 3 - 0 3.0 Under 39 - 28 - 1 03/23 23:15 Full Barcelona (Nio) 1 - 3 A.Bilbao (Aladdin) +0.5 1 - 2 1 - 2 3.5, 4.0 Over 45 - 35 1 - 3 03/23 23:00 Full Villarreal (Pele) 2 - 2 A.Bilbao (Aladdin) 0.0 2 - 3 2 - 3 4.0, 4.5 Under 32 - 41 2 - 2 03/23 22:45 Full A.Madrid (val) 1 - 2 A.Bilbao (Aladdin) +0.5, +1.0 0 - 1 0 - 1 3.5, 4.0 Under 42 - 40 1 - 2 03/23 22:45 Full Barcelona (Nio) 1 - 1 Villarreal (Pele) +0.5 1 - 0 1 - 0 3.0 Under 34 - 39 2 - 1 03/23 22:30 Full A.Madrid (val) 3 - 2 Villarreal (Pele) 0.0, +0.5 1 - 1 1 - 1 3.5, 4.0 Over 42 - 41 3 - 2 03/23 22:15 Full Chelsea (val) 0 - 0 Rapid Vienna (Nio) -0.5 0 - 1 0

Based on the actual size of text shown in the top row. Example: you need a 3/32” text size, and your final plot scale is 1/4” – find the top row for 3//32″ and scale factor of 48 – and note the DIMSCALE. You will also need to specify 3/32” in with text settings in Dimstyle (DDIM) dialog.Drawing ScalesDIMSCALE(factor)1/64”1/32”1/16”3/32”1/8”3/16”1/4”3/8”1/2”3/te4”1”1/16” = 1’-0”19236121824364872961441921/8” = 1’-0”961 1/2369121824364872963/16” = 1’-0”64124681216243248641/4” = 1’-0”483/41 1/234 1/26912182436481/2” = 1’-0”243/83/41 1/22 1/434 1/2691218243/4” = 1’-0”161/41/211 1/22346812161” = 1’-0”123/163/83/41 1/81 1/22 1/434 1/269121-1/2” = 1’-0”81/81/41/23/411 1/2234683” = 1’-0”41/161/81/43/81/23/411 1/2234Updating the scale of dimensions in AutoCAD (DIM UPDATE ALL)First, select all the dimensions that need to be updated with the cursor or the CTRL+A command to select all dimensions in the drawing. Next, type DIM UPDATE ALL in the command line and press Enter. AutoCAD will update all selected dimensions with the current dimension style settings, including the CAD scale factor.Once the update is complete, the dimensions will be adjusted to the correct CAD scale. This command is particularly useful for forcing an update after making changes to the drawing scale or when changing the drawing units or the drawing size.