| """ | |
| Dynamic Routing Between Capsules | |
| https://arxiv.org/abs/1710.09829 | |
| """ | |
| import torch | |
| import torch.nn as nn | |
| import torch.optim as optim | |
| import torch.nn.functional as F | |
| import torchvision.transforms as transforms |
| # The two-pass and Welford's method implementations were taken | |
| # verbatim from Wikipedia: | |
| # | |
| # https://en.wikipedia.org/wiki/Algorithms_for_calculating_variance | |
| # | |
| # Note that in addition to the numerical stability benefits of Welford's | |
| # algorithm, the other benefit is that it's an online algorithm, so | |
| # variance update with additional data has an incremental cost, | |
| # without the need to recompute on all the data. | |
| # |
| # Find the location on the pythonpath from which | |
| # the package was imported. This helps debug pythonpath | |
| # priority-related conflicts. | |
| def pkg_loc(module_name): | |
| module = __import__(module_name, globals(), locals(), [], -1) | |
| return module.__file__ |
This text is the section about OS X Yosemite (which also works for macOS Sierra) from https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/#mac-os-x
The last time i visited this link it was dead (403), so I cloned it here from the latest snapshot in Archive.org's Wayback Machine https://web.archive.org/web/20170523131633/https://docs.basho.com/riak/kv/2.1.4/using/performance/open-files-limit/
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
| .global _start | |
| _start: | |
| LDR R0,=matrix0 | |
| LDR R1,=matrix1 | |
| LDR R2,=matrix2 | |
| LDR R3,=matrix3 | |
| @ Load Q0-Q3 with the data |
| .global main | |
| .func main | |
| main: | |
| LDR R0, =random_seed | |
| LDR R0, [R0] | |
| MOV R1, #num_elements | |
| BL _rng_loop | |
| LDR R0, =unordered_msg | |
| BL printf |
| mkdir ~/vim | |
| cd ~/vim | |
| # Staically linked vim version compiled from https://github.com/ericpruitt/static-vim | |
| # Compiled on Jul 20 2017 | |
| curl 'https://s3.amazonaws.com/bengoa/vim-static.tar.gz' | tar -xz | |
| export VIMRUNTIME="$HOME/vim/runtime" | |
| export PATH="$HOME/vim:$PATH" | |
| cd - |
| def find_ngrams(input_list, max_n): | |
| return [map(lambda x: list(x), zip(*[input_list[i:] for i in range(n)])) for n in range(1, max_n+1)] |
