search for: saving

rucker222 wrote: > The drop down layer selection menu at the top left of the screen directly above where the drawing 1 tab is opens upwards off of the screen once the drawing has a few layers on it. jjmckenzie wrote: > Log file please. I loaded a drawing with plenty of layers and then clicked on the layer drop down menu a couple of times before exiting ProgeCAD. Log file below. (sorry

...03:1050:0200.0001: hiddev0,hidraw0: USB HID v1.00 Device [Yubico Yubico Gnubby (gnubby1)] on usb-0000:00:14.0-2/input0 [ 9.784456] Console: switching to colour frame buffer device 240x67 [ 9.816297] i915 0000:00:02.0: fb0: i915drmfb frame buffer device [ 25.087400] thunderbolt 0000:06:00.0: saving config space at offset 0x0 (reading 0x15eb8086) [ 25.087414] thunderbolt 0000:06:00.0: saving config space at offset 0x4 (reading 0x100406) [ 25.087419] thunderbolt 0000:06:00.0: saving config space at offset 0x8 (reading 0x8800006) [ 25.087424] thunderbolt 0000:06:00.0: saving config space a...

...uite quickly considering the volume of evidential data in my work. My unix shell prompt returns. Uh oh. See what I did there? I typed 'save' when I meant 'save.image'. What does that give me? A 42 byte, empty, latest.RData, and because there was no warning or error I quit without saving it again. Oops. Massive Data Loss. Is there any reason why save(file="file.RData") couldn't warn or error if you try and save nothing? There's no obvious check in the R code for save. Barry PS the above scenario is fictional. When did I last have a good day?

When dealing with object holding pointers that are only valid during a single session, it would be convenient to exclude them from being saved with the session image. (I am assuming that `quit` calls `save.image` before quitting or is it internal?) Currently they are saved with the pointer converted to NULL. Its a bit surprising for users not realizing the object is no longer valid. My thought is

...e structure and save the output and plot of the model. In this example i am using a rpart decision tree. The only problem i am having is integrating the parameter into the internal object name when tying to save it. Solving this one porblem will help me start blasting though 100's of models and saving their output for later use. I would call the script from command line as Rscript file_name.R argument for this example Rscript rpart_code.R Kyphosis #/bin/R args <- commandArgs(TRUE) # Read the argument require(rpart, quietly = TRUE) #for this example lets use the kyphosis data in the rp...

...01: hiddev0,hidraw0: USB HID v1.00 Device [Yubico Yubico Gnubby (gnubby1)] on usb-0000:00:14.0-2/input0 > [ 9.784456] Console: switching to colour frame buffer device 240x67 > [ 9.816297] i915 0000:00:02.0: fb0: i915drmfb frame buffer device > [ 25.087400] thunderbolt 0000:06:00.0: saving config space at offset 0x0 (reading 0x15eb8086) > [ 25.087414] thunderbolt 0000:06:00.0: saving config space at offset 0x4 (reading 0x100406) > [ 25.087419] thunderbolt 0000:06:00.0: saving config space at offset 0x8 (reading 0x8800006) > [ 25.087424] thunderbolt 0000:06:00.0: saving...

Hello, I have the following structure: model foo has_many :bars:, :dependent => true end model bar belongs_to :foo end In my action, when i try to save foo: def save begin f = foo.new f.a = 5 begin b = bar.new b.a = 10 f.bars << b rescue Exception => exc ... end f.save! <-- This does not happen

Dear R-users, I am trying to write a wrapper function around save() that will report the file which is being saved to. So I thought that the followintg would do the trick, but it doesn't. I understand that 'y' is somehow not visible inside save.verbose, but don't know how to fix this. save.verbose <- function(..., file) { cat("save.verbose:", file, "\n")

> rucker222 wrote: > The convert PDF to DXF function does not work (found in the file menu). Below is the output at the Command line when I try to use it. > > Command : _PDF2CAD > 1Vbi file not found > > there does not appear to be an error to copy from the terminal. jjmckenzie wrote: > Interesting. This looks like a 'file not found error' but the first part

Hi, I'm new to Linux and even newer to wine. I'm using the latest release of wine 1.3.20 on U10.10 - the Maverick Meerkat. I work as an AutoCAD Draft Person and as much as I have fallen in love with my Ubuntu OS I am really disappointed with the lack of quality CAD software. I came across ProgeCAD (2010 Pro) on a couple of forums and saw in the AppDB section that ProgeCAD has some

Hi, If anyone has some time to help with my problem that would be really good :) I am getting a "stack level too deep" error when saving an object to the database when it is has a has_one relationship to another object I wish to save and associate after it. If goes a little like this class Quote < ActiveRecord::Base belongs_to :eventdetail has_many :bookings # An eventdetail belongs to either a quote or booking class...

I have changed the default in save() to compress = !ascii. This seems quite safe, as almost always save() is called explicitly and people will appreciate that it might take a little time to save large objects (and depending on your system, compression could even be faster). Should we also change the default in save.image()? That is almost always used implicitly, via q(), a menu .... There

Hi, I've been slowly transitioning to saving sets of objects for a project using save() rather than cluttering my workspace and then doing save.image() However, sometimes after I have done say: save(x,y,z, file='work.Rda') and I reload it a little later and I see that I also want to save object p. Currently I need to do: save(x,y...

...led [ 11.976011] pcieport 0000:00:01.0: PME: Spurious native interrupt! dmesg.3_usb_key_yanked.txt https://pastebin.com/m7QLnCZt I yanked the USB key during boot, that seemed to help unlock things with 5.7, but did not with 5.8. It's hung on a loop of: [ 11.262854] nvidia-gpu 0000:01:00.3: saving config space at offset 0x0 (reading 0x1ad910de) [ 11.262863] nvidia-gpu 0000:01:00.3: saving config space at offset 0x4 (reading 0x100406) [ 11.262869] nvidia-gpu 0000:01:00.3: saving config space at offset 0x8 (reading 0xc8000a1) [ 11.262874] nvidia-gpu 0000:01:00.3: saving config space at o...

...30:04 Creating disk layout 2017-02-19 01:30:04 Preparing layout directory. 2017-02-19 01:30:04 Including layout/save/GNU/Linux/15_save_diskbyid_mappings.sh 2017-02-19 01:30:05 Saved diskbyid_mappings 2017-02-19 01:30:05 Including layout/save/GNU/Linux/20_partition_layout.sh 2017-02-19 01:30:06 Saving disk partitions. 2017-02-19 01:30:08 Including layout/save/GNU/Linux/21_raid_layout.sh 2017-02-19 01:30:08 Saving Software RAID configuration. /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /us...

https://bugzilla.netfilter.org/show_bug.cgi?id=1750 Bug ID: 1750 Summary: 'ipset save' does not save in format loadable by systemd (it saves in 'ipset list' format) Product: ipset Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal

Hi, Today I came upon unexpected R behaviour. I did some modelling and the result was R object, about 28MB size (nested list, with matrixes as list elements). When I was saving the session with save.image, the resulting .RData file was 300MB. There were no other large objects: > sum(sapply(ls(),function(x)eval(parse(text=paste("object.size(",x,")",sep=""))))/1024^2) [1] 30.10540 The interesting thing, then I removed the large object with...

...em using this: d.eta <- load(file="D:/Simulation Results/sim 9-23-11 deta") I got the following: > class(d.eta) [1] "character" > d.eta [1] "d.eta" Why didn't it load the original object that I tried to save (the array)? Is the problem with how I'm saving or how I'm loading? Any explanation would be greatly appreciated. And to head off this question, I did check after the simulation, before saving, and the d.eta object is an array of numbers. Thanks, Mitch

Is there a way to save EVERYTHING in R? Hi all, Could you please shed some lights on me about this? I am trying to see if there is a way to save EVERYTHING in R to a file, something like "save.image"... But "save.image" doesn't save environment variables such as those properties that are obtained using "Sys.getenv()" function... So is there a way to save

On Tue, Sep 08, 2020 at 01:51:19AM +0200, Karol Herbst wrote: > oh, I somehow missed that "disp ctor failed" message. I think that > might explain why things are a bit hanging. From the top of my head I > am not sure if that's something known or something new. But just in > case I CCed Lyude and Ben. And I think booting with > nouveau.debug=disp=trace could already