Unexpected error: Tensor Tensor("dense_1/BiasAdd:0", shape=(?, 3), dtype=float32) is not an element of this graph.
To Fix:
Make sure to include the following global:
import tensorflow as tf
global graph,model
graph = tf.get_default_graph()
And surround the prediction as such:
with graph.as_default():
segment = self.model.predict(features)
While attempting to install a package from gem, I encountered this issue:
sudo gem install dashing
Building native extensions. This could take a while...
ERROR: Error installing dashing:
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from extconf.rb:2:in `'
Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.2.3 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/eventmachine-1.2.3/ext/gem_make.out
Simply to solve this you just need to install ruby-dev packages on ubuntu:
sudo apt-get install ruby-dev
The problem you have encountered is basically the package, or dependencies that are conflicting or broken and are therefore “held”.
You can check what (if any) packages are held using the following command:
dpkg --get-selections | grep hold
or
apt-mark showhold
If there’s no packages, or no output. That means it’s probably a dependency issue which apt-get isn’t able to resolve. apt-get is actually pretty bad at dealing with the dependencies and it’s often easier to try install via aptitude (an alternative to apt-get, which is widely regarded as a better solution to the default apt-get.
Solution:
First install aptitude:
sudo apt-get install aptitude
and then install the package:
sudo aptitude install [package_name]
Error:
When trying to run Node-RED I encountered the following error: Essentially it’s missing the module “express”, as can be seen by the 5 line.
module.js:340
throw err;
^
Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/alex/Apps/node-red/node-red-0.9.1/red.js:19:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
Fix:
In order to fix it, simply install the missing module using the following command.
npm install express
Note: If you’re getting several of these errors (express, nopt, when, uglify-js, clone, ws, etc) in a row after you’ve download and tried to run Node-RED, you might have missed the step to install all the packages:
npm install --production
Activator error “Failed: error: SBT did not send a reply to our request, perhaps it was killed or failed to start”.
This may be because SBT isn’t installed, SBT is a “simple build tool” for scala which isn’t packaged with the main binaries. You can download and install the latest SBT from the official page, installing it fixed the issue for me in Activator.
When running
sudo apt-get update
or attempting to update via the Update Manager in Linux Mint (13), I was fronted with the following error:
Failed to fetch http://packages.linuxmint.com/dists/deb ... tion-en_US Unable to connect to packages.linuxmint.com:http:
Failed to fetch http://packages.linuxmint.com/dists/deb ... slation-en Unable to connect to packages.linuxmint.com:http:
Failed to fetch http://packages.linuxmint.com/dists/deb ... tion-en_US Unable to connect to packages.linuxmint.com:http:
Failed to fetch http://packages.linuxmint.com/dists/deb ... slation-en Unable to connect to packages.linuxmint.com:http:
Failed to fetch http://packages.linuxmint.com/dists/deb ... tion-en_US Unable to connect to packages.linuxmint.com:http:
Failed to fetch http://packages.linuxmint.com/dists/deb ... slation-en Unable to connect to packages.linuxmint.com:http:
Some index files failed to download. They have been ignored, or old ones used instead.
This is caused by missing repositories which are either old, broken or currently down. In order to fix it, simply run:
sudo apt-get update fix-missing
If this option doesn’t work, try changing the repository mirrors with the following guide.
While trying to compile some code on MPLAB X I came across this link error, stating that my #pragma config bits were full or sections of them were overlapping other sections.
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link Error: region FOSC is full (dist/default/production/can_to_serial.production.elf section __FOSC)
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link Error: region FWDT is full (dist/default/production/can_to_serial.production.elf section __FWDT)
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link Error: region FBORPOR is full (dist/default/production/can_to_serial.production.elf section __FBORPOR)
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link Error: section .config_MCLRE%10 [f80004 -> f80005 ] overlaps section __FWDT [f80004 -> f80005 ]
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link Error: section .config_WDT%11 [f80002 -> f80003 ] overlaps section __FOSC [f80002 -> f80003 ]
/Applications/microchip/xc16/v1.11/bin/bin/../bin/elf-ld: Link terminated due to previous error(s).
make[2]: *** [dist/default/production/can_to_serial.production.hex] Error 255
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2
BUILD FAILED (exit value 2, total time: 1s)
After some time scratching my head I realised the issue was that configuration bits were being set twice. Simply I had to remove them. I also moved all configuration bits to a separate header which is only included in the main c source file to avoid future issues.
#include
#include
#include
// FOSC
#pragma config FPR = XT_PLL4 // Primary Oscillator Mode (XT w/PLL 4x)
#pragma config FOS = PRI // Oscillator Source (Primary Oscillator)
#pragma config FCKSMEN = CSW_FSCM_OFF // Clock Switching and Monitor (Sw Disabled, Mon Disabled)
// FWDT
#pragma config FWPSB = WDTPSB_16 // WDT Prescaler B (1:16)
#pragma config FWPSA = WDTPSA_512 // WDT Prescaler A (1:512)
#pragma config WDT = WDT_OFF // Watchdog Timer (Disabled)
// FBORPOR
#pragma config FPWRT = PWRT_64 // POR Timer Value (64ms)
#pragma config BODENV = BORV20 // Brown Out Voltage (Reserved)
#pragma config BOREN = PBOR_ON // PBOR Enable (Enabled)
#pragma config LPOL = PWMxL_ACT_HI // Low-side PWM Output Polarity (Active High)
#pragma config HPOL = PWMxH_ACT_HI // High-side PWM Output Polarity (Active High)
#pragma config PWMPIN = RST_IOPIN // PWM Output Pin Reset (Control with PORT/TRIS regs)
#pragma config MCLRE = MCLR_DIS // Master Clear Enable (Disabled)
// FGS
#pragma config GWRP = GWRP_OFF // General Code Segment Write Protect (Disabled)
#pragma config GCP = CODE_PROT_OFF // General Segment Code Protection (Disabled)
// FICD
#pragma config ICS = ICS_PGD // Comm Channel Select (Use PGC/EMUC and PGD/EMUD)
// Configuration settings
_FOSC(CSW_FSCM_OFF & FRC_PLL16); // Fosc=16x7.5MHz, Fcy=30MHz
_FWDT(WDT_OFF); // Watchdog timer off
_FBORPOR(MCLR_DIS); // Disable reset pin
int main(){
// ... code continues here
#include
#include
#include "config.h"
#include
int main(){
// ... code continues here
// FOSC
#pragma config FPR = XT_PLL4 // Primary Oscillator Mode (XT w/PLL 4x)
#pragma config FOS = PRI // Oscillator Source (Primary Oscillator)
#pragma config FCKSMEN = CSW_FSCM_OFF // Clock Switching and Monitor (Sw Disabled, Mon Disabled)
// FWDT
#pragma config FWPSB = WDTPSB_16 // WDT Prescaler B (1:16)
#pragma config FWPSA = WDTPSA_512 // WDT Prescaler A (1:512)
#pragma config WDT = WDT_OFF // Watchdog Timer (Disabled)
// FBORPOR
#pragma config FPWRT = PWRT_64 // POR Timer Value (64ms)
#pragma config BODENV = BORV20 // Brown Out Voltage (Reserved)
#pragma config BOREN = PBOR_ON // PBOR Enable (Enabled)
#pragma config LPOL = PWMxL_ACT_HI // Low-side PWM Output Polarity (Active High)
#pragma config HPOL = PWMxH_ACT_HI // High-side PWM Output Polarity (Active High)
#pragma config PWMPIN = RST_IOPIN // PWM Output Pin Reset (Control with PORT/TRIS regs)
#pragma config MCLRE = MCLR_DIS // Master Clear Enable (Disabled)
// FGS
#pragma config GWRP = GWRP_OFF // General Code Segment Write Protect (Disabled)
#pragma config GCP = CODE_PROT_OFF // General Segment Code Protection (Disabled)
// FICD
#pragma config ICS = ICS_PGD // Comm Channel Select (Use PGC/EMUC and PGD/EMUD)
If you encounter a problem similar to the following, where you’re missing the libx264 codec try this solution.
avconv -r 10 -i image%06d.jpg -r 10 -vcodec libx264 -crf 20 -g 15 timelapse1.mp4
avconv version 0.8.6-6:0.8.6-0ubuntu0.12.10.1, Copyright (c) 2000-2013 the Libav developers
built on Apr 2 2013 17:02:16 with gcc 4.7.2
Input #0, image2, from 'image%06d.jpg':
Duration: 00:02:21.20, start: 0.000000, bitrate: N/A
Stream #0.0: Video: mjpeg, yuvj420p, 2592x1944, 10 fps, 10 tbr, 10 tbn, 10 tbc
Unknown encoder 'libx264'
In order to acquire libx264, on Debian based distros (Ubuntu, Mint, Raspbian) install the following package:
sudo apt-get install libavcodec-extra-53
After a couple of hours trying to get a USB device (USB-to-Serial FTDI) working in VirtualBox with OSX host and Ubuntu 12.10 guest and receiving an error message similar to the follow:
usb 6-3: new full speed USB device number 24 using ohci_hcd
usb 6-3: device not accepting address 24, error -110
hub 6-0:1.0: unable to enumerate USB device on port 2
It turns out, the issue lies with VirtualBox, when the machine is given more than 1 processor it fails to properly mount any USB device. The only fix I have found to work is to simply reduce the number of processors back to 1. Once it’s returned the USB devices work simply by mounting them the usual way, from the VirtualBox menu > Devices > USB Devices >.
If anyone find a better solution, be sure to comment below.
Over the weekend I’ve been playing around with the Raspberry Pi and lighttpd in order to get a little webserver running. lighttpd seemed to be a common choice, thanks to it’s simplicity and lightweightness (*possibly not a real word). There’s a plethora of examples of getting it up and running, which isn’t too difficult, most notably the one over at Penguin Tutor covers most everything. This gets you to the point where you have the webserver with mySql and php set up.
However, for me at least, this was only accessible from localhost, i.e I could only view the webserver on the Pi itself. After a few hours messing around, setting up a static ip on the router and making sure that port 80 was open on the router, and configuring lighttpd.conf, I realised that it was certainly a network issue. On further investigation, I discovered that iptables (the linux kernel firewall) was to blame. In order to get the server viewable from outside localhost, and also globally I needed to allow the port in iptables rules, which I did with the following command (ran on the Pi):
sudo iptables -A INPUT -m state --state NEW -p tcp --dport 80 -j ACCEPT
Now, this command isn’t set in stone, after a reboot it’ll disappear. In order to save the configuration, once it’s working, just run the following commands:
Save the iptables to firewall.conf and place it in /etc/
sudo iptables-save > firewall.conf
sudo cp firewall.conf /etc/firewall.conf
sudo rm firewall.conf
Now create a file in /etc/network/if-up.d/ called iptables:
sudo nano /etc/network/if-up.d/iptables
And add this content, this will load the iptables config file you saved earlier on boot:
#!/bin/sh
iptables-restore < /etc/firewall.conf
Save and exit (Ctrl+X then press Y and hit return)
Next, make the file executable:
sudo chmod +x /etc/network/if-up.d/iptables
Now you're done, it should be safe to reboot and the iptables will be loaded.