forked from swar/Swar-Chia-Plot-Manager
-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yaml.default
176 lines (157 loc) · 7.94 KB
/
config.yaml.default
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
# This is a single variable that should contain the location of your chia executable file. This is the blockchain executable.
#
# WINDOWS EXAMPLE: C:\Users\Swar\AppData\Local\chia-blockchain\app-1.1.5\resources\app.asar.unpacked\daemon\chia.exe
# LINUX EXAMPLE: /usr/lib/chia-blockchain/resources/app.asar.unpacked/daemon/chia
# LINUX2 EXAMPLE: /home/swar/chia-blockchain/venv/bin/chia
chia_location:
manager:
# These are the config settings that will only be used by the plot manager.
#
# check_interval: The number of seconds to wait before checking to see if a new job should start.
# log_level: Keep this on ERROR to only record when there are errors. Change this to INFO in order to see more
# detailed logging. Warning: INFO will write a lot of information.
check_interval: 60
log_level: ERROR
log:
# folder_path: This is the folder where your log files for plots will be saved.
folder_path: S:\Chia\Logs\Plotter
view:
# These are the settings that will be used by the view.
#
# check_interval: The number of seconds to wait before updating the view.
# datetime_format: The datetime format that you want displayed in the view. See here
# for formatting: https://docs.python.org/3/library/datetime.html#strftime-and-strptime-format-codes
# include_seconds_for_phase: This dictates whether seconds are included in the phase times.
# include_drive_info: This dictates whether the drive information will be showed.
# include_cpu: This dictates whether the CPU information will be showed.
# include_ram: This dictates whether the RAM information will be showed.
# include_plot_stats: This dictates whether the plot stats will be showed.
check_interval: 60
datetime_format: "%Y-%m-%d %H:%M:%S"
include_seconds_for_phase: false
include_drive_info: true
include_cpu: true
include_ram: true
include_plot_stats: true
notifications:
# These are different settings in order to notified when the plot manager starts and when a plot has been completed.
# DISCORD
notify_discord: false
discord_webhook_url: https://discord.com/api/webhooks/0000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
# PLAY AUDIO SOUND
notify_sound: false
song: audio.mp3
# PUSHOVER PUSH SERVICE
notify_pushover: false
pushover_user_key: xx
pushover_api_key: xx
# TWILIO
notify_twilio: false
twilio_account_sid: xxxxx
twilio_auth_token: xxxxx
twilio_from_phone: +1234657890
twilio_to_phone: +1234657890
progress:
# phase_line_end: These are the settings that will be used to dictate when a phase ends in the progress bar. It is
# supposed to reflect the line at which the phase will end so the progress calculations can use that
# information with the existing log file to calculate a progress percent.
# phase_weight: These are the weight to assign to each phase in the progress calculations. Typically, Phase 1 and 3
# are the longest phases so they will hold more weight than the others.
phase1_line_end: 801
phase2_line_end: 834
phase3_line_end: 2474
phase4_line_end: 2620
phase1_weight: 33.4
phase2_weight: 20.43
phase3_weight: 42.29
phase4_weight: 3.88
global:
# These are the settings that will be used globally by the plot manager.
#
# max_concurrent: The maximum number of plots that your system can run. The manager will not kick off more than this
# number of plots total over time.
max_concurrent: 10
jobs:
# These are the settings that will be used by each job. Please note you can have multiple jobs and each job should be
# in YAML format in order for it to be interpreted correctly. Almost all the values here will be passed into the
# Chia executable file.
#
# Check for more details on the Chia CLI here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference
#
# name: This is the name that you want to give to the job.
# max_plots: This is the maximum number of jobs to make in one run of the manager. Any restarts to manager will reset
# this variable. It is only here to help with short term plotting.
#
# [OPTIONAL] farmer_public_key: Your farmer public key. If none is provided, it will not pass in this variable to the
# chia executable which results in your default keys being used. This is only needed if
# you have chia set up on a machine that does not have your credentials.
# [OPTIONAL] pool_public_key: Your pool public key. Same information as the above.
#
# temporary_directory: Only a single directory should be passed into here. This is where the plotting will take place.
# [OPTIONAL] temporary2_directory: Can be a single value or a list of values. This is an optional parameter to use in
# case you want to use the temporary2 directory functionality of Chia plotting.
# destination_directory: Can be a single value or a list of values. This is the final directory where the plot will be
# transferred once it is completed. If you provide a list, it will cycle through each drive
# one by one.
#
# size: This refers to the k size of the plot. You would type in something like 32, 33, 34, 35... in here.
# bitfield: This refers to whether you want to use bitfield or not in your plotting. Typically, you want to keep
# this as true.
# threads: This is the number of threads that will be assigned to the plotter. Only phase 1 uses more than 1 thread.
# buckets: The number of buckets to use. The default provided by Chia is 128.
# memory_buffer: The amount of memory you want to allocate to the process.
# max_concurrent: The maximum number of plots to have for this job at any given time.
# max_concurrent_with_start_early: The maximum number of plots to have for this job at any given time including
# phases that started early.
# stagger_minutes: The amount of minutes to wait before the next job can get kicked off. You can even set this to
# zero if you want your plots to get kicked off immediately when the concurrent limits allow for it.
# max_for_phase_1: The maximum number of plots on phase 1 for this job.
# concurrency_start_early_phase: The phase in which you want to start a plot early. It is recommended to use 4 for
# this field.
# concurrency_start_early_phase_delay: The maximum number of minutes to wait before a new plot gets kicked off when
# the start early phase has been detected.
# temporary2_destination_sync: This field will always submit the destination directory as the temporary2 directory.
# These two directories will be in sync so that they will always be submitted as the
# same value.
- name: micron
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: Z:\Plotter
temporary2_directory:
destination_directory: J:\Plots
size: 32
bitfield: true
threads: 8
buckets: 128
memory_buffer: 4000
max_concurrent: 6
max_concurrent_with_start_early: 7
stagger_minutes: 60
max_for_phase_1: 2
concurrency_start_early_phase: 4
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false
- name: inland
max_plots: 999
farmer_public_key:
pool_public_key:
temporary_directory: Y:\Plotter
temporary2_directory:
- J:\Plots
- K:\Plots
destination_directory:
- J:\Plots
- K:\Plots
size: 32
bitfield: true
threads: 8
buckets: 128
memory_buffer: 4000
max_concurrent: 2
max_concurrent_with_start_early: 3
stagger_minutes: 180
max_for_phase_1: 1
concurrency_start_early_phase: 4
concurrency_start_early_phase_delay: 0
temporary2_destination_sync: false