Displaying 9 results from an estimated 9 matches for "bsdata".
Did you mean:
  sdata
  
2013 Apr 04
5
Help for bootstrapping
...cript out of bounds" Please help! 
library("quadprog")
##############################Preparing for datarawdata = read.table("C:/Desktop/data.txt", header=T)Rf = rawdata[,1]US = rawdata[,2]data = data.frame(Rf,US)OriData = as.matrix(data)
##############################the GetBSData functionGetBSData<-function(data){x = 1:396s = sample(x,6,replace=T)bsdata = data[(s[1]):(s[1]+59),]	for (j in 2:6) {  		a = data[(s[j]):(s[j]+59),]  		bsdata = rbind(bsdata,a)	}return(bsdata)}
#set.seed(1234)#trial<-GetBSData(OriData)
##############################the Minimisation functionOp...
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
 1. Updates the boot protocol to version 2.07
 2. Clean up the existing build process, to get rid of tools/build and
    make the linker do more heavy lifting
 3. Make the bzImage payload an ELF file.  The bootloader can extract
    this as a naked ELF file by skipping over boot_params.setup_sects worth
    of 16-bit setup code.
 4. Update the boot_params to 2.07, and update the
2007 Jun 06
7
[PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
This series:
 1. Updates the boot protocol to version 2.07
 2. Clean up the existing build process, to get rid of tools/build and
    make the linker do more heavy lifting
 3. Make the bzImage payload an ELF file.  The bootloader can extract
    this as a naked ELF file by skipping over boot_params.setup_sects worth
    of 16-bit setup code.
 4. Update the boot_params to 2.07, and update the
2014 May 19
3
Utilizar bs.data
Buen día a todos. Tengo un problema.Podría ayudarme diciendóme cómo se llama la paquetería para encontrar el comando "bs.data", lo he estado buscando para ver como escribir el comando en R y no me aparece una paquetería para ver la descripción. Saludos. 		 	   		  
	[[alternative HTML version deleted]]
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting.  This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
  hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting.  This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
  hardware subarchitecture and some
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting.  This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which adds fields to specify the
  hardware subarchitecture and some
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting.  This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ This patch depends on the cross-architecture ELF cleanup patch. ]
This series updates the boot protocol to 2.07 and uses it to implement
paravirtual booting.  This allows the bootloader to tell the kernel
what kind of hardware/pseudo-hardware environment it's coming up under,
and the kernel can use the appropriate boot sequence code.
Specifically:
- Update the boot protocol to 2.07, which