前段时间接受了美国Wilson Center的环境变化与安全项目博客（The blog of Environmental Change and Security Program)NewSecurityBeat 的Ms. Geng 和Jennifer关于鄂尔多斯市水能源粮食安全的访谈，前几天他们发出来了，今天有时间细看了一遍，发现了一个明显的Bug：竟然出现了鄂尔多斯市要从1500英里之外的新疆巴音郭楞州买水的的话！原来是因为语言交流和地理不熟悉的缘故，把我说的内蒙古的巴彦淖尔市误会成了新疆的巴音郭楞州！也难怪，两个地名本来就有点类似，从我的嘴里说出来估计更分不清！刚才告诉他们，他们说马上修改。 Limited Water for Unlimited Development: QA With Shaofeng Jia https://www.newsecuritybeat.org/2018/06/limited-water-unlimited-development-qa-shaofeng-jia/
Epoch 0/2 ---------- Traceback (most recent call last): File cluster_resnet.py, line 210, in module train_model.train() File cluster_resnet.py, line 174, in train self._train_epoch(epoch) File cluster_resnet.py, line 134, in _train_epoch for data in self.dset_loaders : File /home/linlin/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py, line 201, in __next__ return self._process_next_batch(batch) File /home/linlin/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py, line 221, in _process_next_batch raise batch.exc_type(batch.exc_msg) TypeError: Traceback (most recent call last): File /home/linlin/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py, line 40, in _worker_loop samples = collate_fn( for i in batch_indices]) File /home/linlin/anaconda2/lib/python2.7/site-packages/torchvision-0.1.9-py2.7.egg/torchvision/datasets/folder.py, line 118, in __getitem__ img = self.transform(img) File /home/linlin/anaconda2/lib/python2.7/site-packages/torchvision-0.1.9-py2.7.egg/torchvision/transforms.py, line 34, in __call__ img = t(img) File /home/linlin/anaconda2/lib/python2.7/site-packages/torchvision-0.1.9-py2.7.egg/torchvision/transforms.py, line 156, in __call__ t.sub_(m).div_(s) TypeError: sub_ received an invalid combination of arguments - got (numpy.float32), but expected one of: * (float value) didn't match because some of the arguments have invalid types: (numpy.float32) * (torch.FloatTensor other) didn't match because some of the arguments have invalid types: (numpy.float32) * (float value, torch.FloatTensor other)
We are in the final stage of writing our never-ending paper. Then, I "discovered" a bug in the code (numerical model for ecosystem). I was soooo upset. Eliminated all the snacks I could find in my office, including part of my lunch. Painfully corrected a subroutine; checked, checked, and checked again. TGIF!
The Cyclone III M9K embedded memory blocks may exhibit bit error in which the read bit is a 1 when the expected bit is a 0. The problem is caused by bitline coupling in the read output. The issue is rare and requires the presence of multiple conditions for the M9K block to be susceptible to the bit error. The conditions include the use model of the M9K block, the application data pattern, and the operating conditions.Designs using the M9K blocks in dual clock and widest data width (x32 or x36) modes are most susceptible to the bit error. Designs using the M9K blocks in single clock or narrower data width modes are not affected when operating within data sheet specifications. The problem is highly data-pattern dependent and triggered by specific data bit combinations. Lastly, the problem can be exacerbated by lower temperature and lower voltage operations. The presence of all these conditions does not imply a bit error would necessarily occur. In addition, if some or all of the conditions are not present, the error will not occur.
标签: bug
