Pretty much a self reference post, based on Slicer v. 4.6.
Open the relevant DICOM set.
Open the Crop Volume module
In “Input ROI” dropdown select Create new AnnotationROI
In the slices view adjust the selection so only the interesting area is covered (if you cannot see the delimiters of the crop rectangle, then zoom out the slice view -dragging with right mouse button- until it’s visibile, then move/resize it panning the slice view -dragging with middle mouse button- and then finally rezoom until you are satisfied adjusting the selection)
Click on the Crop! button and see how the slices are cropped to the set area
Open the Editor module (you can select the GenericAnatomyColors palette)
Click on the coloured rectangle on the Label: row, and choose your relevant structure (if you’re here you probably want bone)
Click on ThresholdEffect button (third from last from the effect buttons)
In the Threshold Range input area that just appeared set a starting value of 300 HU (Hounsfield Units) which usually is a good starting density value for bone
You will see the relevant areas blinking in the slices images, and you can adjust the density range by using the small arrow buttons on the side of the lower value of the range
When satisfied, click Apply
Click on the MakeModelEffect button, first from last, and right after click Apply
After a while (depengin on how large is the ROI and how complex is your structure) the rendered model will appear in the 3D view
Click on the SAVE button in the top tools bar, and deselect every entity except the last one (usually named bone if you followed this tutorial), and then choose the STL format in the dropdown on the side (VTK format is selected by default), plus change to your needs the saving folder, and press the Save button
You may also get ‘linux_raid_member‘ instead of ‘isw_raid_member‘, usually it’s the same.
So you probably have run through other tutorials telling you not to mount directly but to mount the raid instead…. but you have no raid!
Maybe though, you HAD a raid back in time, and you removed it leaving the disks as separate storage, and in that case there would be “rogue” raid metadata on the disk that makes linux (mint in my case) think it is a raid, and get confused.
Thanks to Chris_F I finally solved it, you need to use dmraid (install it if it’s not on the system, via apt-get) to remove those orphan tags:
sudo dmraid -rE /dev/sdb
In my case, this instantly showed the disk in file manager.
Connect the SQ8 camera to a USB charger. It cannot be a PC, otherwise it will work as an external drive and show you the contents of the SD, it just needs to receive power.
As soon as you connect the camera you will notice the rear led turning on and cycling through different colors, after which it will turn off: at that moment, the recording will have started.
I still haven’t tested the cyclic recording functionality, but this is supposed to record max 5 minutes chunks of video until the memory runs out, after which it deletes the oldest recordings.
BTW, the correct orientation of the camera is so that the flat side opposite to the buttons side is down, position it elsewhere will give you a rotated video.
On a side note, this camera has a really bad space usage; I put a 32gb card in it, and the file size of the 5 minutes video chunks is 400MB! There is virtually no compression on the video, and the maximum recording time before the oldest files are deleted is less than 6 hours.
90mbs per minute is a really bad stat, in comparison a naruto episode should be 2.4GB if it had the same time/size ratio, it is instead one tenth of that…
I replaced my previous 32GB microsd in my note 3, with a transcend 64GB, and the system asked me if I wanted to use it as extended internal storage. Why not, I never use the sd as swappable storage anyway, and I liked the encrypted storage.
Go ahead an hour, I notice the system filled up 30GB more than the starting space, just stealing it from the sd card for no reason. Also, after rebooting I get a message saying “system has stopped responding”, and swiftkey cannot load languages anymore, disabling altogether the swype function.
I fiddle for good 15 minutes into the settings, finding nothing apparent, until I went into:
Settings > USB and Storage > Internal storage > Options > Migrate
which was supposed to migrate the data from the sd back into the builtin storage.
I started the process and went to sleep (it was late) hoping to find it solved in the morning… too bad! Couldn’t do that, the morning after the internal storage was 100% filled, an error message appeared, and the 60GB sd was still hald full.
The system went from the original 16GB used in the internal storage, to a total of 30GB filled internal storage+roughly 30GB inside the external, which is 60GB used storage… for what? God knows! In the USB&Storage panel of the settings, the details of the used space still amounted to the real space needed, and nothing was there to account for the additional space taken that was reported in the summarized stats…
Hence, I tried copying all the contents from the sd/internal storage to the PC, with the intention of resetting everything afterwards and restoring the data, but using the USB communication resulted in a severely slow transfer speed (we’re talking about a 100Kb file each few seconds, and there were 12GB of data to move).
I tried several times to check and see if I could speed things up, to no avail, so I used the remaining free space on the microsd (I had that, if you don’t you may want to use an OTG cable and a pendrive) to create a ZIP archive (with estrongs) of all the contents of the internal storage, and as a single file like that I could then copy it to my PC at a decent speed.
Once that was done, I wend in settings > USB and storage > SD card > options > format as portable, agreeing to lose all data (I had backed it up anyway), then into recovery I wiped the internal storage, then rebooted to have the changes take effect, and from this state (internal storage almost empty, microsd seen as normal portable storage) I copied over the backed up contents from the previous configuration via normal USB transfer (some files and folders couldn’t be copied, but it was nothing essential).
Up until now eveything looks to have gone back to normal.
I bought a Chauvet Hurricane 1301 for its massive smoke output: my aim is to build a low-cost but extremely effective security and anti theft smoke shield and fog bandit clone, by using nothing more than your average disco fog machine… well, at least a renowned powerful fog machine at that. The specs about the consumption are pretty much the same: 1200W nominal power, and about 50W average when turned on to keep the temperature of the liquid constant. What this system lacks, is the “stamina” that professional systems have, since it won’t fill a room with only the first burst of smoke, but it’s not that much delay between the first puff and the second, and you still get the surprise effect. Ideal for not-so-big rooms.
But you may want to use it to spray smoke when certain events happen, like music timed puffs, or pressure plates, you name it.
There is no immediate way to do it: the wired remote doesn’t provide simple short contacts: none of the pins get shorted when you press the “manual” button there, so it must be a powered remote that sends out powered signals.
Solution: catch the short contact given by the manual switch on the machine’s rear panel.
So what about my homemade smoke shield clone system? I just need to find an alarm sensor to wire up to an arduino, to which will be also wired a relay going to the Hurricane 1301.
This is a report of my own experience with trying to obtain 3d-printer-worth filament out of plastic PET bottles.
I was enthusiastic of this video of the russian survivalist The Lawyer Egorov (who by the way has a supercool channel on youtube for you hardcore people):
who built a contraption to get a very strong string (pun not intended) out of scrap plastic bottles. This, I thought, would have been great fodder for my next to be PET filament machine.
Fast forward to yesterday night/this morning. I had been sourcing parts off the local shops and eletronics from foreign sellers on ebay, and in the spare time finally built this revision of my machine:
After I noticed the PET inside the terminal part of the tube was melting, I started the motor, and this is what happened… not much as the pressure inside the tube was low, there wasn’t much material in the column, and since cutting BY HAND the PET string I had was superboring I didn’t really make the small flakes needed for them to be easily transported.
I increased the quantity of PET flakes in the intake, and pressed them down with a screwdriver handle, so the volume of melted mass on the front increased some.
At this point I decided to place the cap with the nozzle drilled in (1.5mm diameter) and in fact some goo started flowing out and quite rapidly solidifying; the quality of this solidified goo appeared “better”, as the surface was very shiny, but it soon stopped flowing out, and when later I unscrewed the cap I realized it was clogged, as a lot of melted material was idling back there and quickly blobbed outside.
So this is the scenario that presented itself when I uncapped the tube:
At this point I decided my adventure with PET had come to an end. Or rather, my experiments did, since I decided since the night before that I wouldn’t be making PET filament for my 3D printer out of plastic bottles: the processing required to this objective it WAY too much. You need to find a way to satisfactorily grind the plastic, after obviously you cleaned the bottles, and after that you should still dry the flakes at 80°+ degrees to avoid water buildup inside which would drasticaly decrease the final product quality. I would totally prefer spending 20€ per roll of cheap black PLA over this.
You also need to take into account the real life scenario, that is, PRINTING with said filament, because that’s the reason you’re doing it, apart from the fact that you’re just a hopeless nerd like me. A printer’s nozzle is SMALL, and nasty things, even if tiny, can clog it; if said nasty things are inside the filament, then no filament filter is going to hep you; they WILL pile up in the nozzle and sooner than later you’ll have to disassemble the nozzle assembly and do nasty things to take it out, like flaming the nozzle to melt the stuff inside and scooping it out with a piece of filament. Don’t trust the cold pull, it didn’t help me when I needed it. Flaming the nozzle instead, it did help me.
Finally, you have to get a decent diameter filament, AND getting that diameter the most constant possible, because if on one side you can change the extrusion rate in your slicing program to take into account the real filament size, on the other there’s nothing you can do to balance a poorly sized filament, and either you will get extruder skipping steps because of a too big filament, or an extruder skipping steps because the filament is too tiny.
In my brightest dreams I supposed I would be producing crystal clear filament out of plastic bottles, heck maybe even multicolored transparent filament since all bottles are slightly coloured.
Final tecnical considerations
By Ian’s own words, with which I agree, the downfall of this method is the feed system: PET can be a great material, yet a DIY extruder like this one does not allow for much leeway, you need to keep the material flowing forward, and for this you need a granulate which can progress easily in the pipe, and at the same time you also need a constant supply in the back.
So, first off, you need to have a ready made supply of flakes, and obviously cannot just improvise by cutting little piece by little piece on the fly like I did (I was desperate to try, I admit it), and even better you need proper sized pellets, not too large but sufficiently thick! Since PET flakes are flat, they easily adjust in the space between the auger bit and the pipe, and they do not progress further very well; also, if you use a string of PET, it will just roll around the auger in one place (where you feed it through) and not progress forward, but instead slowing down and loading heavily the motor by creating a thick wrap on the drill.
You MIGHT melt bottles whole as they are (how?), and use the obtained solidified blob to create smaller pellets, maybe by hammering the glass-like goo. Still, it will take time, and it’s a messy procedure. Unless you can devise a method to do it without much human intervention, it’s going to cost resources anyway, and you may reconsider the whole thing, and maybe just buy pre-made filament, or a commercial extruder plus finding a local supplier of ABS pellets (not your average ebay seller who asks outrageous sums for 3d printing pellets, but a local plastics industry which works with pellets to make for example injection molded items, where you would pay as low as 2€ per kg of granulate).
I had just made a brand new installation of both Ubuntu trusty and vivid and Debian jessie (tried all of them) on my android phone with Linux Deplow, and installed the LAMP stack via SSH. I wanted Apache to serve files decrypted from an EncFS mount, so I found easier to move the DocumentRoot to a subfolder of my home (by editing /etc/apache2/sites-available/000-default.conf – by the way, this file has changed location quite a bit in the past, being called just default.conf, or being httpd.conf in older versions), and changed Apache’s username to my own (by editing /etc/apache2/envvars).
Well, what happened is that, no matter what I did, I was still getting a 403 Permission denied error, which had nothing to do with EncFS.
By pure chance, I went checking what was inside /etc/apache2/apache2.conf, and other than a reference to envvars for the username and group definitions for the user Apache is run as, scrolling further down there are folders definitions which were, in previous versions, located in the default.conf file. Changing in there the reference to /var/www into the new custom folder made it.
You obviously need to restart Apache after such changes.
This is a personal reminder and also an easier-to-find heads up to those looking for a solution: if you installed linux on Android via Linux Deploy, and find that, no matter how you set rules on AFWall+ you can never get internet to the mounted linux image, unless you disable the firewall altogether (not recommendable since you installed a firewall in the first place), then here is the solution provided in this thread (it’s all due to DNS calls being blocked without a possibility to make them pass through in the vanilla AFWall+).
Under AFWall+ contextual menu, open the custom script editor, and inser these lines: