14%
30.01.2020
45 - IpProtocol: udp
46 FromPort: 0
47 ToPort: 65535
48 CidrIp: 0.0.0.0/0
49 VpcId:
50 Ref: FortiVPC
51
52 InstanceProfile:
53 Properties:
54
14%
04.08.2020
statistic[loops] = { 0 };
41
42 struct timespec tdummy;
43 stats sdummy[4] = { 0 };
44
45 for (unsigned probe = 0; probe < probes; ++probe) {
46 uint64_t accu0 = 0;
47 uint64_t accu1 = 0;
48
14%
30.11.2020
== 0:
08 data = { 'key1' : [10,10.1,10+11j],
09 'key2' : ('mpi4py' , 'python'),
10 'key3' : array([1, 2, 3]) }
11 else:
12 data = None
13 # end if
14
15 data = comm
14%
25.09.2023
for Internal Network
zing.bash -c 4 -op 2 -p 80,443 10.0.0.23
ZING:80/ 10.0.0.23 / Warning:
Error: on 80 is: Active. Continue.
Port: 80: op 1.1. 10.0.0.23 80 Time: 28 ms.
Port: 80: op 1.2. 10.0.0.23 80 Time
14%
05.08.2024
/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.11.2 (main, Feb 17 2023, 09:48:02) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)] (/usr/bin/python3.11)
jinja version = 3.1.2
libyaml = False
14%
02.02.2021
the slices, the higher the precision. You just need to throw CPUs at the problem: in this case, 5 million loops to reach 48 decimal places of accuracy.
Figure 1
14%
17.05.2017
, 5 ) / ( 8, 5 ) }
DATA {
(0,0): 0, 1, 2, 3, 4,
(1,0): 5, 6, 7, 8, 9,
(2,0): 10, 11, 12, 13, 14,
(3,0): 15, 16, 17, 18, 19,
(4,0): 20, 21, 22, 23, 24,
(5,0): 25, 26, 27, 28, 29,
(6,0
14%
08.10.2015
conductors by running multiple instances is not currently supported but is firmly on the roadmap.
Listing 1
Two Server Components and One Client
ps auxww|grep -i magnu
stack 19778 0.1 1.2
14%
01.06.2024
1,
47 MPI_LONG,
48 0,
49 2,
50 MPI_COMM_WORLD);
51 }
52
14%
02.07.2014
WCOLL points:
[laytonjb@home4 ~]$ pdsh -w ^/tmp/hosts uptime
192.168.1.4: 15:51:39 up 8:35, 12 users, load average: 0.64, 0.38, 0.20
192.168.1.250: 15:47:53 up 2 min, 0 users, load average: 0.10, 0.10, 0
