enter image description here
After Colab having an update, I don't know to turn off background execution. Image is the changed runtime setting
Related
I know the output image size requirement is 1440 pixels by 810 pixels #72 dpi.
Problem incurred lots of software and services lock the 16x9 ratio but do not output a standard size.
I want to beable to have the cutting box to zoom in and the cropped image to always be 1440x810#72dpi.
And a feature to move coping box around in the original image would be a nice feature. I just need a working solution that is free temporarily.
Script requires upload of a high quality image and 16x9 cropping box appears over image to crop features out of image and hitting crop would set the box default to 1440x810 so definite cropping box restriction to stop when maximum threshold of conversion is met to not pixelate the output produced image.
Appreciate all the help I can get. Have a wonderful day.
I am in the process of using my android phone and a public computer hence free online service. Normally I would use my photos hope cs6 version but that is not currently available.
I will continue searching but it's like finding a needle in the haystack.
I am hoping another expert has already knows a solution.
I'm trying to run a deep learning code. I usually run in spyder win10. The images obtained thru matplotlib are saved using something like:
plt.savefig('./output/'+filename+'_'+str(num)+'.png',dpi=360)
Occasionally, I would run the code thru the anaconda prompt using:
python abc.py
In this case, the image would appear on-screen. I realise that if I enlarge them, I can get a much clearer image with more details, as compared to the saved image. Why is this so? I have attached some images for comparison
I am running a python-tensorflow-keras jupyter notebook on Colab, training a CNN on Caltech-256 images. The data is loaded from the Caltech site directly to the Colab area with a wget, and never appears on my PC. The notebook includes Tensorboard, and some Callbacks. Obviously, as I first upload the notebook to Colab, that will use some internet bandwidth. I would expect that the rest of the time there should be very little traffic - only enough to update my screen at the end of each epoch (every 600 seconds) or as I click on it. However, there is actually quite a lot of traffic - enough to impact the other people in my house significantly. I believe that the problem is with our upload speed (ie data going from my PC to Colab). I am using Firefox web browser. When I switch to Colab Playground mode, the issue disappears.
What is being uploaded, and why?
Is there any workaround?
I've found the answer here https://github.com/tensorflow/tensorboard/issues/3196
I don't totally understand it, but the workaround listed there works for me:
While the notebook is running, in the tensorboard display, click the settings cog (top right), and uncheck the auto-update box. (You then need to click the refresh icon whenever you want to update your graphs.)
This has to be repeated every time you open the notebook, but it's a small price to pay for family harmony.
Using EDSDK, I want to programmatically set the white balance (RGGB) values of the LiveView stream, and also for the white balance in both JPG (and RAW) images coming from the cam directly. The process of manual white balancing liveview and off-camera images is not completely clear to me and is not really clear in the EDSDK manual.
Through trial and error, I worked my way through calibrating LiveView by issuing the kEdsCameraCommand_DoClickWBEvf command with coordinates on a grey card. This seems to affect liveview all right:
Liveview switches to "ClickWB" (-1) white balance setting
Camera settings remain unchanged: it doesn't change the as-shot values of the camera.
Note that the "manual WB" icon on the camera disappears when setting to "ClickWB", something appears to be wrong.
Apparently, Canon's EOS utility does things slightly different. Using some tracing and polling of PTP events I see that:
Clicking Whitebalance sends a similar ClickWB command to camera.
When clicking "Apply to shot images" sends a command to camera
The camera White Balance stays on value 6 ("Manual","White Point" or "White Paper" depending on the context).
Liveview is also affected as it switches to 6.
Trace shows evidence of "CPtpCamera::TranslateMWb" command, as if there is a command to set the user balance.
The 'raw' White Balance coefficients can apparently be retrieved as EOS displays a warning about the coefficients not being ok.
For RAW images, I worked around white balancing by storing white balance coefficients from a RAW of grey card, and re-applying these coefficients when converting a new image (without grey card) to TIFF. This does not affect the on-camera JPGs, as-shot White Balance and cannot be recovered after reset.
I am stuck when disconnecting/reconnecting camera and (programmatically) apply the previously calibrated or stored WB values. Is this possible, and if so, how do I copy the original white balance values. Anyone here who has experience in manual WBing with EDSDK, care to share the type/order of sharing?
Note:
Canon provides no official technical support whatsoever for the EDSDK
older SDKs were reported to include commands (e.g. in 2.5 kEdsPropID_UserWhiteBalanceData). There must be a replacement for this?
--- update Dec 17 2014 ---
I am currently (indirectly) in "official" contact with Canon's EDSDK developers and currently there is no official way of setting in-camera custom white balance through the EDSDK.
Is there anyway for design purposes that I can have son image host?
Currently if I need to share a desktop screenshot I have to:
open photoshop
Create new image
Past screen capture to new image
save fore web, sometime resize
then upload to an image host
Would be nice if there was something lightweight that would do this whole process in 1 sweep
http://www.pict.com/software