K-Fold 등의 교차 검증 이후 최종적인 best model은 어떻게 선택하나요?

그렇다면 교차검증이란, 다양한 분류 모델을 동일한 데이터셋을 이용하여 '모델간 성능을 비교하는 것'만이 목적이라는 것으로 이해하면 되는 것일까요?예를 들어 이진분류를 하고 싶은데,로지스틱리그레션, 디지전트리, 랜덤포레스트 3가지 모델 중 어떤 것이 좋을까를 결정하기 위하여 3가지 모델에 대하여 KFold를 각각 돌려보고 그 중에 평균값이 좋은 분류 모델을 택하는 과정이다라고 생각하는게 좋겠군요.저는 알고리즘은 정해진 상태에서 학습을 통하여 내부의 파라미터들 (중간 레이어의 weight 같은 것들)의 최적값을 더 잘 찾는 방법 중의 하나로 KFold를 생각했던 것 같습니다.

virtualbox 설치오류

MacOS Catalina에서 실습 중인데, virtualbox 6.1.4, vagrant 2.2.7로 변경하여 진행하고 있습니다. 5.x 대는 Catalina와 궁합이 안맞는 것 같아요. 그런데, vbox + vagrant 설치는 문제가 없는데, ctl.sh에서 Start VM & login을 실행하면 아래와 같이 진행 중에 Guest Addition이 Host에 설치된 Virtualbox와 버전이 안 맞는다는 경고가 뜨고, VM 생성이 성공하기도 실패하기도 합니다. 저의 경우는 docker00.dev는 생성되어 로그인까지 되었고, docker01.dev부터는 virtualbox가 작업 도중에 크래시가 나서 종료됩니다. 아래는 에러 로그입니다. updated: 아 바로 옆 질문에 아래와 같이 버전 미스매치에 대한 오류 로그와 현상이 동일하게 여러분이 언급하고 계시네요. 그냥 참고하시면 되겠습니다. -------- =========================================================== What do you want ? =========================================================== [0] Install the Virtualbox & Vagrant [1] Start VM & login [2] Login to VM [3] Stop VM [4] Reload VM [5] Reboot VM [RM] Remove VM =========================================================== Please insert a key as you need = 1 =========================================================== Bringing machine 'docker01.dev' up with 'virtualbox' provider... ==> docker01.dev: Importing base box 'folimy/Ubuntu1604_with_docker'... ==> docker01.dev: Matching MAC address for NAT networking... ==> docker01.dev: Setting the name of the VM: vagrant_docker_cluster_docker01dev_1584279201875_79335 ==> docker01.dev: Fixed port collision for 22 => 2222. Now on port 2200. ==> docker01.dev: Clearing any previously set network interfaces... ==> docker01.dev: Preparing network interfaces based on configuration... docker01.dev: Adapter 1: nat docker01.dev: Adapter 2: hostonly docker01.dev: Adapter 3: hostonly docker01.dev: Adapter 4: hostonly docker01.dev: Adapter 5: hostonly docker01.dev: Adapter 6: hostonly docker01.dev: Adapter 7: hostonly docker01.dev: Adapter 8: hostonly docker01.dev: Adapter 9: hostonly docker01.dev: Adapter 10: hostonly docker01.dev: Adapter 11: hostonly ==> docker01.dev: Forwarding ports... docker01.dev: 22 (guest) => 2200 (host) (adapter 1) ==> docker01.dev: Running 'pre-boot' VM customizations... ==> docker01.dev: Booting VM... ==> docker01.dev: Waiting for machine to boot. This may take a few minutes... docker01.dev: SSH address: 127.0.0.1:2200 docker01.dev: SSH username: vagrant docker01.dev: SSH auth method: private key docker01.dev: docker01.dev: Vagrant insecure key detected. Vagrant will automatically replace docker01.dev: this with a newly generated keypair for better security. docker01.dev: docker01.dev: Inserting generated public key within guest... docker01.dev: Removing insecure key from the guest if it's present... docker01.dev: Key inserted! Disconnecting and reconnecting using new SSH key... ==> docker01.dev: Machine booted and ready! ==> docker01.dev: Checking for guest additions in VM... docker01.dev: The guest additions on this VM do not match the installed version of docker01.dev: VirtualBox! In most cases this is fine, but in rare cases it can docker01.dev: prevent things such as shared folders from working properly. If you see docker01.dev: shared folder errors, please make sure the guest additions within the docker01.dev: virtual machine match the version of VirtualBox you have installed on docker01.dev: your host and reload your VM. docker01.dev: docker01.dev: Guest Additions Version: 5.2.6 docker01.dev: VirtualBox Version: 6.1 ==> docker01.dev: Setting hostname... ==> docker01.dev: Configuring and enabling network interfaces... ==> docker01.dev: Forcing shutdown of VM... ==> docker01.dev: Destroying VM and associated drives... /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:126:in `[]': no implicit conversion from nil to integer (TypeError) from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:126:in `block in configure_nettools' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:125:in `each' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:125:in `configure_nettools' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:28:in `configure_networks' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/capability_host.rb:111:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/capability_host.rb:111:in `capability' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/guest.rb:43:in `capability' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/network.rb:134:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/

Artifact는 무엇인가요?

Artifact는 참 어려운 단어인듯 합니다. 제가 이해하는 artifact는 maven project에서 사용되는 개념으로만 한정하고 있는데요, maven project의 빌드 결과물로 나오는 개체를 artifact라고 이해하고 있습니다. 그래서 보통 빌드로 나오는 JAR 파일을 artifact라고 이해하라고 하더군요. maven에서 artifactId는 package name인 groupId와 version과 jar 확장자를 제거한 순수한 jar 파일의 부분을 지칭하고요.