In C/C++, you can initialise a struct without giving values for any of the fields:
struct Point {
float x;
float y;
float z;
};
# -o- coding: utf-8 -o- | |
# ISO639 python dict | |
# oficial list in http://www.loc.gov/standards/iso639-2/php/code_list.php | |
ISO639_2 = { | |
'ab': 'Abkhaz', | |
'aa': 'Afar', | |
'af': 'Afrikaans', | |
'ak': 'Akan', | |
'sq': 'Albanian', |
class FullPaths(argparse.Action): | |
"""Expand user- and relative-paths""" | |
def __call__(self, parser, namespace, values, option_string=None): | |
setattr(namespace, self.dest, os.path.abspath(os.path.expanduser(values))) | |
def is_dir(dirname): | |
"""Checks if a path is an actual directory""" | |
if not os.path.isdir(dirname): | |
msg = "{0} is not a directory".format(dirname) | |
raise argparse.ArgumentTypeError(msg) |
% Copyright (c) 2010 Michael Ummels <michael@ummels.de> | |
% | |
% Permission to use, copy, modify, and/or distribute this software for any | |
% purpose with or without fee is hereby granted, provided that the above | |
% copyright notice and this permission notice appear in all copies. | |
% | |
% THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES | |
% WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF | |
% MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR | |
% ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES |
void blendWithMask(cv::Mat &base, cv::Mat &src, cv::Mat &mask, cv::Mat &out){ | |
char ch = base.channels(); | |
double alpha = 0; | |
for( int y = 0; y < base.rows; y++ ){ | |
uchar* pBS = base.ptr<uchar>(y); | |
uchar* pSR = src.ptr<uchar>(y); | |
uchar* pMK = mask.ptr<uchar>(y); | |
uchar* pOU = out.ptr<uchar>(y); | |
for( int x = 0; x < base.cols*ch; x++ ){ | |
int ix = x / ch; |
A CQF elective with Dr. Yves J. Hilpisch, The Python Quants GmbH
General resources:
# https://stackoverflow.com/a/44672195/3013522 | |
git reset --soft HEAD~1 |
The intention of this document is to provide some guidance and suggestions to customers who are wondering how they should structure organizations and teams in their GitHub Enterprise environment. The idea isn't to give hard and fast rules on which approach is better than the other, but to give examples of when one approach might be preferable to another depending on the use case.
________________
| Org |
| ______ |
| | |\ |
| | Repo | \ |
mv -v ~/Library/Application\ Support/.lpxuserdata ~/.Trash |